MCP Server

The server is not deployed yet

The server code is ready (apps/mcp in the monorepo), the public address will appear once it is deployed alongside the documentation site. The URL below is the target one.

MCP (Model Context Protocol) is the protocol an agent uses to call an external tool while it works. Unlike AI Skills and LLMs.txt, which ship with a library version and are read as a static reference, the MCP server answers live: the component API is always current, so are the tokens of the current theme and the search over the documentation.

Setup

Claude Code:

claude mcp add --transport http cds https://cds-preview-docs.vercel.app/mcp

Cursor / VS Code — MCP servers config:

{
  "mcpServers": {
    "cds": { "type": "http", "url": "https://cds-preview-docs.vercel.app/mcp" }
  }
}

No authorization required: the server is reachable from the internal network.

Tools

Tool	Arguments	What it does
list_components	query?	Component catalog by category: name, purpose, link to the docs
get_component_api	name, section?	Contract from meta.json: props / events / slots / exposed, subcomponents included
get_component_examples	name, demo?	Live examples (the same demo SFCs as on the site and in Storybook): list or code
search_docs	query, limit?	Full-text search over component pages and guides
get_tokens	group?	Design tokens: color palette and themes
check_migration	name	What changed in CDS 4 for a component or a theme (an excerpt from MIGRATION.md)

The data version matches the version of @central-design-system/components at the time of the last release and is reported in the MCP handshake.

Example requests

A plain phrasing is enough for the agent — it picks the tool itself:

• "What props does CdsSelect have?" → get_component_api
• "Show me a form with validation built on CDS" → search_docs + get_component_examples
• "What changed in CdsList when moving to CDS 4?" → check_migration
• "What colors are in the palette?" → get_tokens

When to use MCP, Skills or llms.txt

• Skills — a procedure: how to build UI, migrate, review. A skill walks the agent through the steps and pulls in references as needed.
• MCP — fresh data on demand: API, examples, tokens, search, migration. Works in any client with MCP support, no packages to install.
• llms.txt — a flat catalog for agents without skills and MCP.

A "skill + MCP" combination is the norm: the skill carries the rules, MCP answers pinpoint questions about the current version.