Basalt
Pull Basalt design tokens, components, icons, and accessibility data into Claude, Cursor, or Windsurf while building UI.
Overview
Basalt is a MCP server for the Build phase that serves design tokens, components, icons, and accessibility data to coding agents via basalt.run.
What is this MCP server?
- Exposes design tokens, components, icons, and a11y data through MCP
- SSE remote at basalt.run with Bearer API key authentication
- Explicit support positioning for Cursor, Claude, and Windsurf
- Backed by the basalt-run/design-system GitHub repository
- Version 1.0.0 server entry tied to basalt.run product settings
- Four documented resource families: design tokens, components, icons, and a11y data
- SSE MCP endpoint at https://basalt.run/api/mcp
- Server version 1.0.0 in MCP registry metadata
Community signal: 1 GitHub stars.
What problem does it solve?
Agents hallucinate colors, component APIs, and a11y details when the real design system lives outside the repo.
Who is it for?
Solo builders on Basalt who want Cursor, Claude, or Windsurf to implement UI with live system metadata.
Skip if: Teams without a Basalt account or projects that do not use Basalt-managed tokens and components.
What do I get? / Deliverables
After registration with your Basalt API key, the agent pulls authoritative token and component data so frontend code matches your design system.
- Agent-readable design tokens and component specifications aligned to Basalt
- Icon and a11y reference data usable during UI implementation
- Fewer design-to-code mismatches on solo frontend sprints
Recommended MCP Servers
Journey fit
Basalt feeds live design-system facts into implementation, which is core Build work on the frontend surface of a solo SaaS or landing product. Frontend subphase is where tokens, components, icons, and a11y constraints must match the system your agent is codegen against.
How it compares
Hosted design-system MCP bridge, not a generic Figma scraper or backend database server.
Common Questions / FAQ
Who is Basalt for?
Indie developers and small teams using Basalt who want design tokens, components, icons, and a11y data inside Claude, Cursor, or Windsurf.
When should I use Basalt?
Use it during Build frontend work whenever you implement or refactor UI that must stay aligned with your Basalt design system.
How do I add Basalt to my agent?
Add the SSE MCP remote https://basalt.run/api/mcp with Authorization Bearer and your API key from https://basalt.run Settings, then reload the client.