Privacy-friendly analytics only with consent. No ads, no cross-site tracking. Read the privacy policy.
Set up the Slipstream UI MCP server to give AI agents validated access to component specifications.
Try the MCP tools — live, in your browser
same /registry manifests the server reads · loading…Browse every component with package/tier filters.
tool resultGET /registry — list_components
// loading registry…
MCP (Model Context Protocol) is a protocol that allows AI agents to query external tools and data sources. The Slipstream UI MCP server provides tools for AI agents to:
Install the MCP server as a development dependency:
pnpm add -D @slipstream-ui/mcp-server
Add the MCP server to your Claude Desktop configuration:
// claude_desktop_config.json{"mcpServers": {"slipstream-ui": {"command": "node","args": ["path/to/node_modules/@slipstream-ui/mcp-server/dist/index.js"]}}}
Add to your Cursor settings:
// settings.json{"mcpServers": {"slipstream-ui": {"command": "node","args": ["path/to/node_modules/@slipstream-ui/mcp-server/dist/index.js"]}}}
Configure in your Windsurf settings file.
Any client that speaks MCP over stdio can launch the published binary with npx -y @slipstream-ui/mcp-server. OpenCode reads the server from opencode.json:
// opencode.json{"mcp": {"slipstream-ui": {"type": "local","command": ["npx", "-y", "@slipstream-ui/mcp-server"],"enabled": true}}}
With the package installed in the project, point at the local binary instead to skip the download: node node_modules/@slipstream-ui/mcp-server/dist/index.js.
List all available Slipstream UI components with optional filters.
// List all componentslist_components()// Filter by packagelist_components(package="@slipstream-ui/core")// Filter by tierlist_components(tier="atom")// Combine filterslist_components(package="@slipstream-ui/ai", tier="molecule")
Semantic-ish keyword search over components by capability — faster than browsing when the agent knows what the UI should do, not what it is called.
// Find streaming-capable componentssearch_components(query="streaming chat")// Find citation components and cap the result countsearch_components(query="citations grounding", limit=5)
Start from the goal, not a component name. Returns a coherent set with a reason and a docs URL for each component, plus a note to read the manifest before generating code.
recommend_components(goal="agent dashboard with human approvals")// Limit and filter to the AI packagerecommend_components(goal="RAG answer with citations", limit=4, package="@slipstream-ui/ai")
Get the complete COMPONENT_MANIFEST for a specific component.
// Get button manifestget_component_manifest(componentId="button")// Get message manifestget_component_manifest(componentId="message")
Fetch runnable examples (basic, composition, edge cases) plus composition rules and anti-patterns straight from the manifest, so the agent copies patterns that actually compile.
get_usage_examples(componentId="select-menu")get_usage_examples(componentId="dialog")
Validate generated JSX against the component manifest before it ships. The validator reports unknown (hallucinated) props, values outside a documented enum, missing required props, missing compound roots, and icon-only controls without an accessible name, and returns the manifest's anti-patterns so the agent can re-check intent. Every issue carries a fix string with the concrete next action, so the agent can correct the code without a second round trip. It does not type-check expressions or render the component.
validate_usage(componentId="button",code="<Button variant='primry'>Save</Button>")// Returns:// {// valid: false,// usageCount: 1,// issues: [{// severity: "error",// message: "Invalid value \"primry\" for prop \"variant\" ... Allowed values: default, destructive, outline, ...",// fix: "Set variant=\"primary\" (nearest allowed value; allowed: default, primary, ...)."// }],// antiPatternsToCheck: [...]// }
Pass files instead ofcode to validate a whole tree in one call. Every Slipstream component in each file is inferred from its JSX and checked, and non-Slipstream tags are reported as skipped rather than flagged:
validate_usage(files=[{ path: "app/page.tsx", code: "<Button variant='outline'>Save</Button>" },{ path: "app/settings.tsx", code: "<Button varient='outline'>Go</Button>" }])// Returns:// {// mode: "tree",// valid: false,// fileCount: 2,// summary: { files: 2, components: 2, errors: 1, warnings: 0, skippedTags: [] },// files: [// { path: "app/page.tsx", valid: true, components: [...] },// { path: "app/settings.tsx", valid: false, components: [...] }// ]// }
Here's how an AI agent might use the MCP server:
// AI Agent Flow:1. Agent: "I need to create a button"MCP: list_components(package="@slipstream-ui/core", tier="atom")→ Returns: Button, Input, Badge, Avatar2. Agent: "Get the button manifest"MCP: get_component_manifest(componentId="button")→ Returns: Full COMPONENT_MANIFEST with props, examples, etc.3. Agent: "Create a primary action button"→ Uses manifest props: variant="default"→ Uses manifest examples: <Button>Click me</Button>→ Follows content guidelines for button text→ Ensures accessibility requirements4. Agent: "Validate before emitting"MCP: validate_usage(componentId="button", code="<Button>Click me</Button>")→ { valid: true, issues: [] }
Tool availability is not a habit. Add an explicit rule to CLAUDE.md, .cursorrules, or AGENTS.md:
# UI componentsThis project uses Slipstream UI. Before writing any component JSX:1. search_components / get_component_manifest for the component you need.2. Follow its props exactly - never invent prop names.3. Run validate_usage on the generated JSX before finishing.4. Respect anti-patterns and composition rules from the manifest.
Every manifest is also served as markdown and as registry JSON. An agent that can fetch a URL gets the same contract without a connection:
GET https://slipstreamui.com/llms.txtGET https://slipstreamui.com/llms-full.txtGET https://slipstreamui.com/llm/components/<id>.mdGET https://slipstreamui.com/registry/<id>.json
When developing the MCP server:
# Build the MCP servercd packages/mcp-serverpnpm build# Test locallynode dist/index.js# The server runs on stdio and responds to MCP protocol messages
Ensure the path to the MCP server executable is correct in your configuration. Use the full path to the built file:
// Instead of:"args": ["@slipstream-ui/mcp-server"]// Use full path:"args": ["/absolute/path/to/node_modules/@slipstream-ui/mcp-server/dist/index.js"]
The MCP server loads manifests directly from the installed packages at startup, so component IDs always match the source of truth. If a component is missing, verify it has a COMPONENT_MANIFEST in its package's src/manifests directory.
Ensure the MCP server has read permissions to access the manifest files in the packages directory.