RMCP.DEV
← Registry

Developer Tools

designsystems.one

Provides access to design system registry and component details for shadcn-style components.

1 endpoint12 known toolsFirst detected June 3, 2026Last detected June 10, 2026

ENDPOINT 1

https://www.designsystems.one/api/mcp

No auth detected

Known tools 12

list_registry

List every shadcn-style component available in the DesignSystems.one registry.

Inferred read-only
get_component

Fetch the full source files for a registry component (e.g.

Inferred read-only
generate_tokens

Generate a complete design-token set in the chosen format.

Inferred read-only
list_design_systems

List every design system in the DesignSystems.one gallery (37+).

Inferred read-only
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.

Inferred read-only
list_patterns

List the 12 cross-system UI patterns documented on the site (data tables, forms, confirmations, empty states, navigation, voice and content, etc).

Inferred read-only
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.

Inferred read-only
list_playbook_chapters

List the eight chapters of the Build playbook (the 90-day path from zero to a system that holds up).

Inferred read-only
get_playbook_chapter

Get the full content of a playbook chapter — sections, takeaways, callouts.

Inferred read-only
search_glossary

Search the design-systems glossary by term or matching content.

Inferred read-only
search_site

Search every section of designsystems.one (pages, foundations, tools, patterns, playbook chapters, design-system breakdowns).

Inferred read-only
list_foundations

List the 11 foundation topics on the site — color, typography, spacing, layout, motion, duration-and-easing, accessibility, principles, voice-and-tone, naming-conventions, maturity-model.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for designsystems.one was fetched 2026-07-28T01:06:53.113Z and is being refreshed.

Trust status Trusted

designsystems.one is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.