Labsco
MCP SERVER

Your design tokens live in Git; this serves them to Cursor, Claude Code and Windsurf so the AI stops inventing hex values.

Design Systems & UI Component Libraries
Summary
Closes the gap between the design file and the generated code.

An AI tool asked for "the action colour" will produce something plausible and wrong; here it resolves the actual chain from component token down to the primitive and returns what your repository says. Cheapest possible integration too — a URL and a key, no local process.

What it is

A hosted MCP endpoint for a Basalt design system. The repository holds the tokens as JSON in the DTCG 2025.10 format, and the server hands those real values to AI coding tools instead of leaving them to guess a colour or a spacing step.

What you get
  • Token values read straight out of the repository: primitives, plus light and dark semantic themes
  • Three tiers resolved end to end — primitive, semantic, component — so a query for a button background returns the raw value behind it
  • Setup as a plain URL entry in Cursor, Claude Code, Claude Design or Windsurf
  • Tokens stay in Git, reviewable in a pull request like any other file
Requirements

No install. Add https://basalt.run/api/mcp to your client and send an `Authorization: Bearer` header with a Basalt API key, which is free from basalt.run. The transport is SSE. MIT licensed; the token repository itself is `@basalt/design-system` at 1.0.13.

Setup effort

One command plus a key — claude mcp add --transport http basalt https://basalt.run/api/mcp --header "Authorization: Bearer bsk_your_key_here", then supply credentials