Svelte MCP

What it does

Svelte MCP is maintained by the Svelte team and gives a coding assistant two things: access to the current Svelte and SvelteKit documentation, and a static-analysis check for Svelte components it has just written. It runs either locally over stdio from the @sveltejs/mcp npm package, or as a hosted endpoint at https://mcp.svelte.dev/mcp.

Four tools are registered in version 0.1.26: list-sections returns the index of documentation sections, get-documentation returns the full text of one or more of them, svelte-autofixer runs the Svelte compiler, a set of custom checks and ESLint over a piece of code and reports issues and suggestions, and playground-link builds a Svelte Playground URL with the code packed into the link itself. Beyond tools, it offers a doc-section resource (svelte://<slug>.md) so a user can attach a specific docs page, and a svelte-task prompt that tells the model which sections exist and when to call each tool.

The documentation is not bundled: the local server downloads the section list from svelte.dev/docs/experimental/sections.json and each page's llms.txt at call time, giving up after 10 seconds per request (utils.ts). The autofixer accepts only Svelte 4 or 5 as desired_svelte_version, and its async option is refused unless the version is 5 (svelte-autofixer.ts). The same package also works as a command-line tool: run with no subcommand it starts the MCP server, while list-sections, get-documentation and svelte-autofixer subcommands print results to the terminal.

What it needs

Local: Node.js with npx, and network access to svelte.dev, since documentation is fetched live. Hosted: an MCP client that can connect to a remote Streamable HTTP server; Codex CLI needs experimental_use_rmcp_client = true in its config.toml per the docs. No account or API key is needed for either.

Limits

Covers only Svelte, SvelteKit and the Svelte CLI documentation. The autofixer works on Svelte 4 or 5 code only, and async mode only with Svelte 5. Documentation lookups fail when svelte.dev cannot be reached within 10 seconds. Playground links carry the whole code in the URL, so they can be very long. The hosted server closes its SSE channel at once, so it sends no log messages or list-changed notifications (README).

Who it suits

Suits anyone using an assistant to write Svelte 5 or SvelteKit code who wants it to check its output against the compiler and the current docs rather than older training data. The hosted endpoint needs no install; pick the local npx form if you prefer the analysis to run on your own machine. It reads docs and analyses code you pass in; it does not edit your project. For Svelte work it is the official option; community servers we hold such as mcp-svelte-docs only serve documentation and lack the autofixer.