Fabkit MCP Server

Fabkit MCP Server

A Model Context Protocol server for the Fabkit Svelte 5 UI library, deployed as a Cloudflare Worker.

Agents (Claude, Cursor, Copilot…) can call this server to get accurate, up-to-date Fabkit documentation without hallucinating component names, props, or icon names.

Tools exposed

Quick start

1. Install dependencies

npm install

2. Run locally

npm run dev
# → http://localhost:5173

3. Deploy to Cloudflare Workers

npm run deploy
# → https://fabkit-mcp.fabricators.dev

Connecting to Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "fabkit": {
      "url": "https://fabkit-mcp.fabricators.dev/mcp",
      "transport": "http"
    }
  }
}

Connecting to Cursor

In .cursor/mcp.json:

{
  "mcpServers": {
    "fabkit": {
      "url": "https://fabkit-mcp.fabricators.dev/mcp"
    }
  }
}

Connecting to Gemini CLI

In ~/.gemini/settings.json:

{
  "mcpServers": {
    "fabkit": {
      "url": "https://fabkit-mcp.fabricators.dev/mcp"
    }
  }
}

Note: Gemini CLI does not support the transport key — use only url.

Connecting to GitHub Copilot CLI

In ~/.copilot/mcp-config.json:

{
  "mcpServers": {
    "fabkit": {
      "type": "http",
      "url": "https://fabkit-mcp.fabricators.dev/mcp",
      "tools": ["*"]
    }
  }
}

Alternatively, run /mcp add inside the CLI and fill in the fields interactively.

Connecting to VS Code

In .vscode/mcp.json (workspace) or ~/.config/Code/User/mcp.json (global):

{
  "servers": {
    "fabkit": {
      "type": "http",
      "url": "https://fabkit-mcp.fabricators.dev/mcp"
    }
  }
}

Note: VS Code uses "servers" (not "mcpServers") as the root key.

Connecting to Continue.dev

In ~/.continue/config.json:

{
  "mcpServers": [
    {
      "name": "fabkit",
      "type": "streamable-http",
      "url": "https://fabkit-mcp.fabricators.dev/mcp"
    }
  ]
}

Connecting to Windsurf

In ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "fabkit": {
      "serverUrl": "https://fabkit-mcp.fabricators.dev/mcp"
    }
  }
}

Note: Windsurf uses "serverUrl" (not "url") for remote HTTP servers.

MCP Protocol

The server implements MCP 2024-11-05 over Streamable HTTP (POST /mcp).

All requests are JSON-RPC 2.0:

# Initialize
curl -X POST https://fabkit-mcp.fabricators.dev/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{}},"id":1}'

# List tools
curl -X POST https://fabkit-mcp.fabricators.dev/mcp \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":2}'

# Call a tool
curl -X POST https://fabkit-mcp.fabricators.dev/mcp \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"get_component","arguments":{"name":"Button"}},"id":3}'

Extending the knowledge base

Edit src/knowledge.ts — add entries to the COMPONENTS array or extend ALL_ICONS.
Edit src/tools.ts — add new entries to the PATTERNS object.
Then redeploy: npm run deploy.

Architecture

src/
  index.ts      ← Cloudflare Worker entry, routing, CORS
  mcp.ts        ← JSON-RPC 2.0 dispatch, tool registry
  knowledge.ts  ← All Fabkit docs embedded as typed data
  tools.ts      ← Tool implementations (pure functions)

Everything is stateless — no KV, no R2, no external APIs.
The Worker cold-starts in < 5ms because all knowledge is bundled inline.