Your Lexington MCP key is ready

Find your key - It is on the confirmation page you just saw and in the Polar receipt email. It starts with LEXMCP-. You can always see it again in the Polar customer portal.
Add the server to your client - Paste the key into the bearer header. Cursor: .cursor/mcp.json. Claude Code: claude mcp add. Codex: ~/.codex/config.toml. The exact snippets are on the MCP page and in the documentation.
Ask for a page - Something like: “Build a landing page for a bookkeeping app with the Lexington MCP. Warm, serious, not dark.” The agent reads the guidelines itself, picks a theme, pulls the sections and fills them.

Good to know

One theme per page. Mixing themes reads as two websites. The agent knows this; if it wanders, say “stay in one theme”.
The section is right. Copy, images, links and data are yours to change. Spacing, type and layout are the theme’s. If something looks off after install, it is almost always a missing font or the tokens file, not the section.
Not Astro? Ask for flat HTML: “use format html”. You get the same section with every class expanded, ready for React, Vue or Svelte. The host still needs Tailwind CSS 4 and the theme’s tokens file.
Fair use is 1,000 section pulls per key per month, which is a lot of websites. Team plans have five keys.

Email michael[@]lexingtonthemes.com. Cancelling is one click in the Polar portal; what the agent already wrote into your projects stays yours.