mcp s

This MCP server provides access to the Svelte 5 documentation through the MCP protocol. It exposes a route for context-enabled queries so tools integrated with MCP (like editors or assistants) can fetch up-to-date documentation and context for Svelte 5. To use it, start the built server from your environment (after building the monorepo). Once running, configure your MCP client (e.g., Claude Desktop or Cline) to point to the server's entry (the built index.js) as shown in the installation instructions. You can then query for documentation snippets, API details, and contextual guidance directly from your editor or tooling via the MCP protocol.

Prerequisites:

• Git
• Node.js and npm/yarn (for pnpm you should install pnpm)
• PNPM (pnpm is used in this monorepo)

Installation steps:

1. Install pnpm globally if you don't have it: npm install -g pnpm
2. Clone the MCP servers monorepo: git clone <repository-url> cd <repository-directory>
3. Install dependencies for all packages in the monorepo: pnpm install
4. Build all packages (produces the build outputs used by MCP servers): pnpm run build
5. Run the Svelte Docs Server (from its built path or integrate into your MCP setup): node /path/to/svelte-docs-server/build/index.js You can also configure an MCP launcher to start this script directly as shown in the mcp_config example.
6. Optional: for ongoing development with auto-rebuild, you can use: pnpm run watch

Notes & tips:

• The server in this repo is organized as a monorepo using PNPM workspaces. Build before running to ensure the /build/index.js entry exists.
• If you’re using Claude Desktop, place the MCP config in the location specified (MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%/Claude/claude_desktop_config.json) and reference the built entry for the svelte-docs-server.
• The example configuration in the README uses the built index.js as the command. Replace /path/to/svelte-docs-server/build/index.js with the actual absolute path on your system.
• If you encounter port conflicts, set a specific PORT in the mcp_config env (e.g., PORT=8080) and ensure your client points to that port.
• For debugging, you can use the MCP Inspector tool to inspect requests and responses; start it with pnpm run inspector as described in the repository.