MCP for coding agents
Let Claude Code, Cursor and others use your design system.
Basemode's MCP server lets coding assistants such as Claude Code and Cursor look up tokens, check their own code and ask your team for what's missing, instead of inventing a value.
Hosted
Every plan includes the hosted server. Create a developer key in your design system, then:
claude mcp add --transport http basemode \
https://api.basemode.io/v1/mcp \
--header "Authorization: Bearer <developer-key>"
A developer key can read the design system but never publish to it. The hosted server always serves the latest tokens, guidelines and components.
Local, with no account
claude mcp add basemode -- uvx --from basemode-tokens \
basemode mcp --tokens src/tokens/basemode.lock.json
This serves the lock file in your repository.
Tools
| Tool | What it answers |
|---|---|
get_design_system | What the system contains: token counts, modes, guidelines and components. Agents call this first. |
search_tokens | Tokens by name or description, such as "primary" or "radius". |
find_token | The token for a raw value, such as #2563EB or 16px. |
check_code | Hard-coded colors, spacing, radii and font sizes in a piece of code, with the token to use instead. |
get_guidelines | The team's written rules for using the system. |
list_components | Components, their status and how to import them. |
check_contrast | WCAG contrast of two colors, given as values or token names. |
report_gap | Tells the design system's team what was missing. With a developer key, it lands in Basemode's Feedback tab. |