The Sora UI docs MCP server gives AI assistants live access to this site — installation guides, primitives, and the component catalog. It runs as a remote HTTP server at https://mcp.soralabs.studio/mcp (no local CLI required).

Capabilities

Tools

Prompts

Resources

How it works in practice

MCP does not auto-suggest Sora components in the editor — there is no autocomplete, component picker, or inline hint while you type JSX. MCP is optional tooling for the AI agent: after you enable a server, the agent can call its tools when your prompt is relevant, but it is neither always-on nor guaranteed on every message.

Two servers, two jobs

Use both if you'd rather the agent call an MCP tool to install than run shadcn/sora-cli itself — register @soralabs in components.json first, see Installation. Most agents with shell access can just run the command get_component_info returns.

What is automatic vs manual

1. Setup (manual, one-time) — Add MCP config (or click Add to Cursor below), then enable the server under Settings → Tools & MCP. Restart Cursor if tools do not appear.

2. During Agent chat (semi-automatic) — The agent may call MCP when it decides it needs live docs — for example, you ask for a scroll-pinned hero and it searches for scroll-gallery. This depends on your prompt, mode (Agent vs Ask), and model; it will not happen on every request.

3. Explicit prompts (most reliable) — Name Sora UI or the task directly: “List installable Sora UI components”, “Get install info for scroll-gallery”, “Get the source code for scroll-gallery”, “Add scroll-gallery from @soralabs and use variant=studio”.

What MCP is not

• Not IDE IntelliSense or Copilot-style inline completions
• Not a replacement for reading source when you already have components in your repo
• Not the same as project rules or skills — those load into context; MCP tools are invoked on demand

Typical workflow

1. Enable sora-ui MCP (+ shadcn MCP too, only if you want tool-call installs)
2. In Agent chat, ask naturally or explicitly:
   - "What Sora component fits a pinned scroll text reveal?"
   - "Install scroll-gallery and show usage with variant=studio"
3. Agent calls sora-ui MCP → reads docs / gets component info → runs
   `npx shadcn@latest add @soralabs/scroll-gallery --yes` (or `sora-cli add`) → writes code in your repo

Add to Cursor

Cursor supports one-click MCP install links. Click below — Cursor opens a prompt to add the remote server, then enable it under Settings → Tools & MCP.

Manual configuration (Cursor)

Add this to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

After saving, enable the server in Settings → Tools & MCP and restart Cursor.

Add to Claude Code

Claude Code is Anthropic's official CLI. You can connect via remote HTTP or local STDIO:

Manual configuration (Claude Code)

Add to ~/.claude/settings.json (global) or .claude/settings.json (project):

Add to Claude Desktop

Open the Claude Desktop config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the server under mcpServers. Claude Desktop connects via mcp-remote (recommended for remote endpoints) or local compiled script:

Local Development (STDIO & HTTP)

If you are developing inside the Sora UI monorepo or running a custom self-hosted instance, apps/xmcp compiles both STDIO (dist/stdio.js) and HTTP (dist/http.js) bundles:

cd apps/xmcp
bun install
bun run build       # compiles dist/stdio.js and dist/http.js

• Run STDIO locally: node apps/xmcp/dist/stdio.js
• Run HTTP server locally: bun run start (serves at http://localhost:1337/mcp)
• Development with hot reload: bun run dev

Example prompts

Browse documentation

• List all Sora UI documentation sections
• Search Sora UI docs for text reveal components
• Get the MCP documentation page from Sora UI

UI kit

• Search Sora UI docs for dialog components
• Get the UI kit landing page (ui)
• List the UI section in Sora UI docs

Components catalog

• Search Sora UI components for underline link
• Get the draw-underline-link primitive page
• List the components section in Sora UI docs

Registry install

• List installable Sora UI components
• Get install info for stagger-button
• What dependencies does the scroll-gallery component need?
• Get the full source code for stagger-button
• Add scroll-gallery from @soralabs and wire it into my page with variant=studio

Registry MCP (shadcn)

To add @soralabs/* components from the registry with natural language, configure the shadcn MCP server alongside Sora UI docs MCP.

Automatic configuration

Manual configuration

Install the shadcn package as a dev dependency:

Merge the shadcn entry into your MCP config (example for Cursor):

Register @soralabs in components.json before asking the agent to install components — see Installation.

Troubleshooting

Agent does not use MCP tools

MCP is agent-driven, not automatic. Confirm the server is enabled (green) in Settings → Tools & MCP, use Agent mode (not Ask), and mention Sora UI explicitly in your prompt. Prompts like “Search Sora UI docs for …” or “List installable Sora UI components” are the most reliable way to trigger tool calls.

Server not connecting

Cursor: Confirm sora-ui is enabled in Settings → Tools & MCP, restart Cursor after changing .cursor/mcp.json, and check View → Output → MCP for errors.

Claude Code: Run claude mcp list to verify the server is registered. If missing, re-run claude mcp add --transport http sora-ui https://mcp.soralabs.studio/mcp. Use claude mcp get sora-ui to inspect the saved config.

Claude Desktop: Confirm the JSON in claude_desktop_config.json is valid (no trailing commas), then fully quit and reopen the app.

Tools return no results

• Use list_sections first to see available documentation and components sections
• For component pages, try slugs like text-effect or paths like primitives/accordion

Install link does nothing

Paste the deeplink into your browser address bar, or add the manual JSON config above. See Cursor MCP install links.

Nested sora-ui key in mcp.json

If Cursor shows must have either a command or url and your config looks like "sora-ui": { "sora-ui": { "url": "..." } }, remove the extra nesting — use the manual JSON shape, or click Add to Cursor again on this page (the install link encodes only { "url": "..." }; the name query param supplies the server key).