shadcn-svelte-mcp Svelte Themes

Shadcn Svelte Mcp

Mastra MCP server and tooling for the shadcn-svelte component docs and developer utilities.

#mcp#mcp-server#shadcn#shadcn-svelte#svelte
Download

shadcn-svelte-mcp

Mastra MCP server and tooling that provides real-time access to shadcn-svelte component documentation and developer utilities using web scraping.

Production Deployments

Choose the base host that fits your workflow — both expose the same toolset, but their runtime characteristics differ:

Host Base URL Highlights
Mastra Cloud https://shadcn-svelte.mastra.cloud Primary choice - Zero cold start, maximum responsiveness, and consistently reliable performance. Tool discovery issue has been fixed.
  • Append /api/mcp/shadcn/sse for the SSE transport (best for editors that keep long-lived connections).
  • Append /api/mcp/shadcn/mcp for the HTTP transport (handy for CLIs and quick one-off calls).
  • Mastra Cloud is the recommended primary deployment - it offers zero cold start and maximum responsiveness. Tool discovery issue has been fixed and it can be used reliably.
Endpoint reference & alternates

[!NOTE] This project follows our Code of Conduct and welcomes contributions! See our Contributing Guidelines for details.

This repository contains a Mastra-based MCP server that provides real-time access to shadcn-svelte component documentation using web scraping. Use it in your AI-powered code editor to get instant access to the latest shadcn-svelte component information directly from the official website.

🎉 What's New

  • ✅ Production deployment on Mastra Cloud
  • ✅ Five main MCP tools for comprehensive shadcn-svelte ecosystem support (see 'Available Tools')
  • ✅ Bits UI API documentation - Direct access to underlying component library API docs with AI-optimized content
  • ✅ Advanced fuzzy search with typo tolerance and intelligent suggestions
  • ✅ Lucide Svelte icon search - Browse and search ~1,600 icons (dynamic) with smart filtering
  • ✅ Support for all major AI code editors (Cursor, Windsurf, VS Code, Zed, Claude Code, Codex)
  • ✅ HTTP and SSE transport protocols
  • ✅ Real-time web scraping from shadcn-svelte.com and bits-ui.com

Bits UI Integration

shadcn-svelte components are built on top of Bits UI, the underlying component library that provides the core functionality. This MCP server provides direct access to Bits UI's comprehensive API documentation through AI-optimized content endpoints.

AI-Optimized Content

The bits-ui-get tool fetches content from Bits UI's dedicated /llms.txt endpoints, which provide:

  • Structured API reference tables with Property/Type/Description/Details columns
  • Clean markdown formatting optimized for AI consumption
  • Implementation details and usage examples
  • Data attributes and event handlers documentation
  • Navigation links to related components

This ensures that AI assistants receive the most relevant and well-structured information for implementing shadcn-svelte components correctly.

🔧 Observations & Minor UX Suggestions

  • The shadcn-svelte-icons tool previously showed an awkward message "No icons found matching "undefined"" when explicit names were requested and none were found — this has been fixed so the response now shows No icons found for names: ... instead. ✅
  • Imports in the icons tool are intentionally limited to the first 10 names in the response to keep usage snippets tidy; increase the limit if you need more icons returned (the snippet still only imports the first 10). 💡
  • Imports in the icons tool are intentionally limited to the first 10 names in the response to keep usage snippets tidy; increase the limit if you need more icons returned (the snippet still only imports the first 10). 💡
  • The icons tool now supports importLimit (default 10) and limit (default 100) to control how many icons are returned, and how many are included in import statements.
  • The shadcn-svelte-get tool now respects an optional packageManager parameter and adjusts the installation snippet accordingly (pnpm dlx, yarn dlx, npx, bunx). ✅
  • If you notice any remaining odd messages or install command inconsistencies, please file an issue — we keep the MCP server behavior stable but will gladly refine UX in following pull requests.

Editor Setup

Mastra Cloud is the recommended primary deployment for all editors. It offers zero cold start and maximum responsiveness. SSE works best for editors that keep a persistent connection, while HTTP is handy for one-off requests and scripts. VS Code users can open the Command Palette (Cmd/Ctrl+Shift+P) and run MCP: Add server to paste either URL.

Cursor
  1. Open Cursor Settings (Cmd/Ctrl + ,).
  2. Navigate to "MCP" / "Model Context Protocol" and add a new server configuration.
  3. Mastra Cloud is recommended for zero cold start and maximum responsiveness. Append the SSE or HTTP path as shown in the examples below.

Mastra Cloud — SSE example:

{
  "shadcn-svelte": {
    "type": "sse",
    "url": "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/sse"
  }
}

Mastra Cloud — HTTP example:

{
  "shadcn-svelte": {
    "type": "http",
    "url": "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp"
  }
}

Mastra Cloud is the recommended deployment for reliability and responsiveness.

Windsurf
  1. Edit ~/.codeium/windsurf/mcp_config.json.
  2. Mastra Cloud is recommended for zero cold start and maximum responsiveness. Add the SSE transport as shown:
{
  "mcpServers": {
    "shadcn-svelte": {
      "url": "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/sse",
      "transport": "sse"
    }
  }
}
  1. Save, restart Windsurf, then open mcp.json in Agent mode and click "start".

Use the HTTP variant if you need it:

{
  "servers": {
    "shadcn-svelte": {
      "type": "http",
      "url": "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp"
    }
  }
}
Zed
  1. Open Zed settings (Cmd/Ctrl + ,).
  2. Edit ~/.config/zed/settings.json and add an entry under context_servers:
{
  "context_servers": {
    "shadcn-svelte": {
      "source": "custom",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/sse"
      ],
      "env": {}
    }
  }
}
  1. Save, restart Zed, and confirm the server shows a green indicator in the Agent panel. Zed also offers a UI flow via Settings → Agent to paste either endpoint without editing JSON.

CLI & Agent Configuration

The same base URLs work across CLIs. Mastra Cloud is the recommended primary deployment for the fastest responses with zero cold start.

Claude Code CLI (Anthropic)

  • Global settings (~/.claude/settings.json):

    {
  "mcpServers": {
    "shadcn-svelte": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp"
      ]
    }
  }
}

  • Project-scoped override (.mcp.json):

    {
  "mcpServers": {
    "shadcn-svelte": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp"
      ]
    }
  }
}

    Enable project servers with:

    {
  "enableAllProjectMcpServers": true
}

  • Command palette alternative:

    claude mcp add --transport http shadcn-svelte https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp

  • Use /permissions inside Claude Code to grant tool access if prompted.

OpenAI Codex CLI

Register the Mastra Cloud endpoint for codex or use your own privately hosted MCP endpoint.

codex mcp add shadcn-svelte --url https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/sse
codex mcp list
Gemini CLI (Google)

  1. Create or edit ~/.gemini/settings.json:

    mkdir -p ~/.gemini
nano ~/.gemini/settings.json

  2. Add a configuration. Mastra Cloud example:

    {
  "mcpServers": {
    "shadcn-svelte": {
      "httpUrl": "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp"
    }
  }
}

  3. Prefer the npx mcp-remote command variant if your CLI version expects a command:

    {
  "mcpServers": {
    "shadcn-svelte": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp"
      ]
    }
  }
}

  4. Mastra Cloud is recommended for zero cold start and maximum responsiveness. Restart the CLI to apply changes.

Verification & Quick Tests

  • claude mcp list
  • codex mcp list
  • npx mcp-remote https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp
  • curl -I https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/mcp
  • curl -N https://shadcn-svelte.mastra.cloud/api/mcp/shadcn/sse

Claude Code may prompt for tool permissions — use /permissions or set allowedTools in ~/.claude.json. Editors that maintain long-lived connections should use the SSE URL; quick scripts can stick with HTTP.

Available Tools

Note: The previous 'utility' tool has been split into dedicated tools. Use shadcn-svelte-icons for icon browsing/search, shadcn-svelte-list and shadcn-svelte-get for discovery and docs, shadcn-svelte-search for fuzzy search, and bits-ui-get for underlying API details.

Once installed, your AI assistant will have access to these tools (IDs exactly as exposed by the MCP server):

  1. shadcn-svelte-list — List components, blocks, charts, and docs (returns Markdown lists)
  2. shadcn-svelte-get — Retrieve detailed component/block/doc content as structured JSON (content, metadata, codeBlocks)
  3. shadcn-svelte-icons — Browse and search Lucide Svelte icons by name/tag (returns Markdown with install + usage snippets; accepts an optional names array for explicit icon selection; supports limit (total returned) and importLimit (how many to include in imports); uses dynamic upstream icon data)
  4. shadcn-svelte-search — Fuzzy search across components and docs (returns Markdown for display and a results array for programmatic use)
  5. bits-ui-get — Access Bits UI component API documentation with AI-optimized content from llms.txt endpoints (provides structured API reference tables, implementation details, and clean markdown formatting)

Tool response formats (quick reference)

  • shadcn-svelte-list: Markdown list intended for human display (component names, docs, blocks)
  • shadcn-svelte-get: Structured JSON with content, metadata, codeBlocks (useful for programmatic responses). You can pass an optional packageManager (npm|yarn|pnpm|bun) to render install commands using a preferred package manager.
  • shadcn-svelte-icons: Markdown list with icon names, tag summaries, and an example @lucide/svelte usage snippet. Accepts names: string[] for explicit selection and returns multi-import usage snippets.
  • shadcn-svelte-search: An object with markdown, results (structured), and totalResults
  • bits-ui-get: Structured JSON with AI-optimized content from Bits UI's llms.txt endpoints, including API reference tables and implementation details

Example Usage

After installing the MCP server in your editor, you can ask your AI assistant:

  • "Show me how to install the shadcn-svelte button component"
  • "List all available shadcn-svelte components"
  • "Search for date picker components in shadcn-svelte"
  • "Find all chart components with 'line' in the name"
  • "How do I customize the theme for shadcn-svelte?"
  • "What are the props for the Dialog component?"
  • "Search for Lucide icons related to 'user profile'"
  • "Find all arrow icons in Lucide Svelte"
  • "Search for Lucide icons related to 'user profile'" — uses shadcn-svelte-icons tool
  • "Find components matching 'date picker'" — uses shadcn-svelte-search tool (returns markdown and structured results)
  • "Get specific icons 'arrow-right' and 'user' with pnpm as package manager" — { names: ['arrow-right','user'], packageManager: 'pnpm' } (call shadcn-svelte-icons)
  • "Get the installation docs for dashboard-01 using yarn" — { name: 'dashboard-01', type: 'component', packageManager: 'yarn' } (call shadcn-svelte-get)
  • "What are the API details for the Button component?" — uses bits-ui-get tool for underlying Bits UI implementation details
  • "Show me the Button component's props and events" — uses bits-ui-get tool with AI-optimized content from llms.txt

Local Development

Want to run the MCP server locally or contribute to the project?

Contents

  • src/ - Mastra bootstrap, MCP servers, tools, and agents
  • src/services/ - Web scraping services for real-time documentation fetching
  • src/mastra/tools/ - Tools that expose component discovery, fetching and utilities
  • src/mastra/agents/ - Specialized AI agent for shadcn-svelte assistance
  • scripts/ - Version management and automation scripts

Quick start (development smoke-test)

  1. Install dependencies (using your preferred package manager).
# npm
npm install

# or bun
bun install

# or pnpm
pnpm install
  1. Run the development smoke-test (recommended):
# Starts Mastra in dev mode; this repo's smoke-test expects a short run to detect runtime errors
npm run dev

Useful scripts

  • npm run dev - Start Mastra in development mode (recommended smoke-test).
  • npm run build - Build the Mastra project for production.
  • npm run start - Start the built Mastra server.
  • npm run check-versions - Check if package.json and mcp-server.ts versions match (fails if mismatched).
  • npm run sync-versions-auto - Check versions and auto-sync if mismatched (package.json is source of truth).
  • npm run sync-versions - Sync versions from latest git tag to both files.

MCP Architecture

This project exposes a production-ready MCP Server that makes shadcn-svelte documentation and tools available to AI code editors.

What this means:

  • MCP Server (src/mastra/mcp-server.ts) - Exposes four shadcn-svelte tools to external MCP clients (Cursor, Windsurf, VS Code, etc.)
  • No MCP Client needed - This project only provides tools, it doesn't consume tools from other servers

The server is deployed at https://shadcn-svelte.mastra.cloud and exposes tools via HTTP and SSE transports.

For a detailed explanation of MCP concepts, see MCP_ARCHITECTURE.md.

Project Architecture

Core Components

  • Mastra Framework: Orchestrates agents, workflows, and MCP servers
  • MCP Server: Exposes tools to AI code editors via HTTP/SSE protocols
  • Web Scraping Services: Multi-strategy approach for fetching documentation:
    • Direct .md endpoint fetching for shadcn-svelte components
    • AI-optimized /llms.txt endpoint fetching for Bits UI API documentation
    • Crawlee (Playwright) for JavaScript-heavy pages (charts, themes, blocks)
    • Cheerio + Turndown for simple HTML pages
  • Intelligent Caching: 3-day TTL cache with memory and disk storage
  • Component Discovery: Dynamic scraping of component registry from shadcn-svelte.com
  • Advanced Search: Fuse.js-powered fuzzy search with typo tolerance

Key Features

  • Real-time Documentation: Always fetches latest content from shadcn-svelte.com and bits-ui.com
  • Bits UI API Access: Direct integration with underlying component library documentation via AI-optimized llms.txt endpoints
  • Multi-strategy Fetching: Handles different page types (SPA, static, JS-heavy)
  • Intelligent Caching: Reduces API calls while ensuring freshness
  • Lucide Icon Search: Browse and search ~1,600 Lucide Svelte icons with smart filtering by name and tags
  • Comprehensive Testing: Edge case coverage and integration tests
  • Automated Versioning: Semantic release with version synchronization
  • Production Deployment: Mastra Cloud hosting with monitoring

Conventions & notes

  • Tools are implemented under src/mastra/tools and should use zod for input validation
  • Web scraping services are implemented under src/services/ and use Crawlee (with Playwright) for real-time documentation fetching from JavaScript-heavy pages
  • Intelligent caching is used to improve performance and reduce API calls
  • Tools follow Mastra patterns using createTool with proper input/output schemas

Development tips

  • Node >= 20.9.0 is recommended (see package.json engines)
  • When adding tools, follow the patterns in src/mastra/tools/shadcn-svelte-get.ts and shadcn-svelte-list.ts
  • After making changes, run the 10–15s smoke-test via npm run dev to surface runtime integration issues early
  • Set up proper Firecrawl API credentials for web scraping functionality
  • The system uses intelligent caching - clear cache if you need fresh data during development

License

This project is licensed under the MIT License - see the LICENSE file for details.

Contributing

We welcome contributions! Please read our Contributing Guidelines and Code of Conduct before getting started.

Contact

For more details:

  • MCP Prompts System: See MCP_Prompts_System.md for comprehensive documentation on the MCP prompt system
  • MCP Architecture: See MCP_ARCHITECTURE.md for detailed explanation of MCP server vs client
  • Web scraping services: See src/services/ for Crawlee-based real-time documentation fetching implementation
  • AI assistant guide: See .github/copilot-instructions.md

Top categories

tailwinddaisyuiadmin templatepopupmdsvexportfolioblogformecommerceuicarouselauthdarkseoimagerouting
Loading Svelte Themes