Finished Tailwind sections and design systems from every Lexington theme, as Astro, React or HTML.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Bearer <licence key> for paid themes. Leave it out for the free theme and the catalogue.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
The theme's design system: typography recipes, what each colour scale means, spacing rhythm, components, do and don't, plus roles.json (the same as data: action, panel, ink, muted, rule, radius, heading and body recipes, measured from the sections). Read before changing anything visual, reskinning, or aliasing the palette onto a host.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http lexington https://mcp.lexingtonthemes.com/mcp
Headers
Authorization (optional, not in the config above): Bearer <licence key> for paid themes. Leave it out for the free theme and the catalogue.The theme's design system: typography recipes, what each colour scale means, spacing rhythm, components, do and don't, plus roles.json (the same as data: action, panel, ink, muted, rule, radius, heading and body recipes, measured from the sections). Read before changing anything visual, reskinning, or aliasing the palette onto a host.
| Argument | Type | Description |
|---|---|---|
| theme* | string |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"theme"
],
"properties": {
"theme": {
"type": "string"
}
}
}Read this first. How to install, fill and fit Lexington sections into an Astro + Tailwind project, and what not to change.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}One or more sections with every file they need (fundations, icons, placeholder images), each with the path to write it to. Shared files are sent once. Ask for the whole page in one call. format 'tsx' returns React components (Next, Vite, Remix), format 'html' flat HTML with the Tailwind classes expanded (Vue, Svelte, plain HTML). Both are standalone sections only; parts have no flat export.
| Argument | Type | Description |
|---|---|---|
| ids* | array | Section ids from search_sections, in page order, e.g. ['brightlight/hero-1', 'brightlight/faq-1'] |
| have | array | Install paths already written in this project; they are omitted from the reply. |
| format | string | astro (default): .astro components with fundations. tsx: React components, no props, classes expanded. html: flat HTML, classes expanded. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"ids"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 12,
"minItems": 1,
"description": "Section ids from search_sections, in page order, e.g. ['brightlight/hero-1', 'brightlight/faq-1']"
},
"have": {
"type": "array",
"items": {
"type": "string"
},
"description": "Install paths already written in this project; they are omitted from the reply."
},
"format": {
"enum": [
"astro",
"tsx",
"html"
],
"type": "string",
"description": "astro (default): .astro components with fundations. tsx: React components, no props, classes expanded. html: flat HTML, classes expanded."
}
}
}The companion skill for a theme, to write into the project so the agent keeps the theme's rules on every later edit without calling this server: the theme's own design skill (typography, colour, spacing, components, do and don't) plus the shared Lexington sections skill (fill, fit, reskin, port). Call once per project after the first get_sections.
| Argument | Type | Description |
|---|---|---|
| theme* | string | |
| target | string | Where skills live in this project. cursor: .cursor/skills/ (default). claude: .claude/skills/. agents: one AGENTS.md block to append, for clients without skills. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"theme"
],
"properties": {
"theme": {
"type": "string"
},
"target": {
"enum": [
"cursor",
"claude",
"agents"
],
"type": "string",
"description": "Where skills live in this project. cursor: .cursor/skills/ (default). claude: .claude/skills/. agents: one AGENTS.md block to append, for clients without skills."
}
}
}Once per project, per theme: tokens.css and Fonts.astro to write, plus the two setup steps. Call before the first get_sections for a theme.
| Argument | Type | Description |
|---|---|---|
| theme* | string |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"theme"
],
"properties": {
"theme": {
"type": "string"
}
}
}Every theme available, with who it is for, its visual personality, fonts, light/dark mode and section count. Pick one theme per page.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}Find sections by role and description. Returns id, group and a one-line description. Use the ids with get_sections.
| Argument | Type | Description |
|---|---|---|
| mode | string | Only themes with this colour mode |
| group | string | Section group: heros, features, pricing, ctas, faqs, testimonials, landing |
| query | string | Words like 'hero split screenshot', 'pricing two tiers', 'faq' |
| theme | string | Theme slug to restrict to |
| include_parts | boolean | Also return cards that take props (kind: part). Default false. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"mode": {
"enum": [
"light",
"dark",
"light+dark"
],
"type": "string",
"description": "Only themes with this colour mode"
},
"group": {
"type": "string",
"description": "Section group: heros, features, pricing, ctas, faqs, testimonials, landing"
},
"query": {
"type": "string",
"description": "Words like 'hero split screenshot', 'pricing two tiers', 'faq'"
},
"theme": {
"type": "string",
"description": "Theme slug to restrict to"
},
"include_parts": {
"type": "boolean",
"description": "Also return cards that take props (kind: part). Default false."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 7, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.