@adres/dls-mcp
v1.0.0
Published
MCP server exposing design system components, tokens, and guidelines to AI coding assistants.
Readme
dls-mcp (Adresx DLS)
MCP server exposing the Adresx DLS (design language system) component APIs, design tokens, usage guidelines, and accessibility rules to AI coding assistants (Claude, Cursor, VS Code, and other MCP-compatible clients).
The programmatic server id is dls-mcp; the product name is Adresx DLS.
Connected clients should call these tools when the user mentions either name,
ADRES DLS, or the design system. A Figma URL plus Adresx DLS and a brand
should call start_figma_prototype (asks new prototype vs existing app
before scaffolding).
See blueprint/project-plan.md for the full product plan.
Commands
- Dev server:
npm run dev - Build:
npm run build - Start (built server):
npm run start - Typecheck:
npm run typecheck
See AGENTS.md for the full command list (transports, env vars, MCP Inspector).
Connecting a client
Local (stdio)
For Claude Code, Cursor, Claude Desktop, or any other MCP client running on your machine, paste this config. No clone or local build is required:
{
"mcpServers": {
"adresx-dls": {
"command": "npx",
"args": ["-y", "@adres/dls-mcp"]
}
}
}The config key (adresx-dls) is the label shown in the client. dls-mcp still
works as the key if you already have it configured.
KNOWLEDGE_BASE_PATH and BRAND_KNOWLEDGE_BASE_PATH are optional - only set
them to override the knowledge files resolved from the installed
@adres/design-system and @adres/brand-contract packages.
From a clone
If you are developing this repo, run npm run build so dist/index.js exists,
then point the client at the compiled file:
{
"mcpServers": {
"adresx-dls": {
"command": "node",
"args": ["/absolute/path/to/dls-mcp/dist/index.js"]
}
}
}Hosted (streamable HTTP)
For the deployed instance on Vercel. Every request requires a bearer token -
ask a maintainer for the current MCP_BEARER_TOKEN value, then configure your
client:
{
"mcpServers": {
"adresx-dls": {
"url": "https://dls-mcp.vercel.app/mcp",
"headers": {
"Authorization": "Bearer <token>"
}
}
}
}Requests without a valid Authorization header get a 401. Keep the token out
of shared chats or commits - treat it like any other credential.
Publishing
Maintainers publish @adres/dls-mcp to npm with:
npm publish --access publicDo not publish from /implement or a feature branch by default. This repo only
publishes after an explicit yes in the current chat. Use
npm publish --dry-run to check the tarball without uploading.
