← designsystems.one
INDIVIDUAL MCP TOOL
generate_tokens
Generate a complete design-token set in the chosen format.
Input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- A tool name, description or schema mentions credentials.
Parent endpoint
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.designsystems-one]
url = "https://www.designsystems.one/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"designsystems-one": {
"type": "http",
"url": "https://www.designsystems.one/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: designsystems-one
Remote MCP URL: https://www.designsystems.one/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"designsystems-one": {
"url": "https://www.designsystems.one/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"designsystems-one": {
"type": "http",
"url": "https://www.designsystems.one/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "designsystems-one",
"transport": "streamable-http",
"url": "https://www.designsystems.one/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
list_registry— List every shadcn-style component available in the DesignSystems.one registry.get_component— Fetch the full source files for a registry component (e.g.list_design_systems— List every design system in the DesignSystems.one gallery (37+).get_design_system— Get the full editorial breakdown of a specific design system — origin, governance model, known-for moments, underrated parts, watch-outs, components catalog, token snapshot, external links.list_patterns— List the 12 cross-system UI patterns documented on the site (data tables, forms, confirmations, empty states, navigation, voice and content, etc).get_pattern— Get the full pattern entry — description, signals to watch for, what typically breaks, and references to specific design systems that document the pattern well.list_playbook_chapters— List the eight chapters of the Build playbook (the 90-day path from zero to a system that holds up).get_playbook_chapter— Get the full content of a playbook chapter — sections, takeaways, callouts.