Skip to content

MCP Server

Connect your AI editor to Sisyphos UI in 30 seconds. The hosted Model Context Protocol endpoint streams component docs, props, accessibility notes, and demos straight to Claude, Cursor, VS Code, Windsurf, and any other MCP-aware client.

LiveStreamable HTTP · No auth · Read-only
https://www.sisyphosui.com/api/mcp

What is the Sisyphos MCP?

The Model Context Protocol is an open standard for connecting AI assistants to live, structured data sources. Point your AI editor at the Sisyphos endpoint and Claude, Cursor, VS Code, or any MCP-aware client can pull the canonical component docs — props, accessibility notes, framework usage — straight from the registry, the moment a release ships.

01

Always fresh

The server reads the same registry that powers this docs site. New release? Your editor picks it up the next turn — no client update.

02

Zero install

Hosted, remote, Streamable HTTP. No npm package, no stdio process, no version drift between your editor and the registry.

03

All three frameworks

Every tool accepts an optional framework argument. The assistant scopes its output to React, Vue, or Angular automatically.

Endpoint

Authentication: none. The server is read-only and rate-limited at the edge. If your editor needs an API key field, leave it blank.

https://www.sisyphosui.com/api/mcp

Editor setup

Pick your editor — paste the snippet, restart, and the assistant has every Sisyphos component at its fingertips.

From any project root, register Sisyphos as a project- or user-scoped MCP server:

terminal
claude mcp add --transport http sisyphos https://www.sisyphosui.com/api/mcp

Verify with `claude mcp list` — you should see sisyphos as connected. Tools become available the next time Claude starts a turn.

Available tools

Six read-only tools. Every tool that returns component data accepts an optional framework argument (react, vue, or angular) so the assistant can scope its output to the user's stack.

list_components

List every Sisyphos UI component grouped by category. Optional filters: category, framework.

get_component

Full markdown docs for a component — install, import, framework usage, props, anatomy, keyboard, accessibility.

search_components

Substring search over component name, slug, and description. Pair with framework to narrow to a binding.

get_component_demo

Code-only demo snippets for a component, optionally scoped to a framework. Use when you only want the snippet, not prose.

get_installation

Install command, peer requirements, and base CSS import for the chosen framework. Run this before generating any code.

get_changelog

Recent Sisyphos UI releases with version, date, summary, and headline highlights.

Prompts

add-sisyphos-componentCurated

Walks the assistant through the canonical “install + import + idiomatic usage” flow for a given slug and framework. Surface it from your editor's prompts picker once the server is connected.

Verify your connection

Hit the endpoint directly with curl to confirm it's reachable. Healthy servers respond with a JSON-RPC tools/list result containing the six tools above — the same response shape every MCP client consumes during the handshake:

snippet.bashbash
curl -sS -X POST https://www.sisyphosui.com/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
Was this page helpful?