Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
The official Svelte MCP server providing docs and autofixing tools for Svelte development
Facts
- MCP registry
dev.svelte/mcp· 0.1.26- Endpoint
https://mcp.svelte.dev/mcp- Packages
npm@sveltejs/mcp stdio- Website
- svelte.dev/docs/mcp/overview
- npm / week
- 26k
- GitHub stars
- 330
- Registry entry
- updated 7 Aug 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under svelte.dev, a namespace the registry only gives to whoever proves they control that domain.
- It's in real use: 26,085 npm downloads a week, 330 GitHub stars.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 4 · about 6,155 tokens of context · checked 2 hours ago
| Tool | What it does | Hint |
|---|---|---|
get-documentationRetrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "cli/overview"). Can accept a single section name or an array of sections. Before running this, make sure to analyze the users query, as well as the output from list-sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to fetch all relevant runes, and so on. Before calling this tool, try to implement Svelte components using your own knowledge and the `svelte-autofixer` tool, since calling this tool is token intensive. | Retrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "cli/overview"). Can accept a single section name or an array of… | read-only |
list-sectionsLists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get_documentation to fetch ALL relevant sections at once. | Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze… | read-only |
playground-linkGenerates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code in the playground before calling this tool. NEVER use this tool if you have written the component to a file in the user project. The playground accept multiple files so if are importing from other files just include them all at the root level. | Generates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code… | read-only |
svelte-autofixerSvelte Autofixer | Given a svelte component or module returns a list of suggestions to fix any issues it has. This tool MUST be used whenever the user is asking to write svelte code before sending the code back to the user | read-only |
What https://mcp.svelte.dev/mcp answered to tools/list, asked without credentials over MCP 2026-07-28. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 4 warnings · 1 note
- warnTC06get-documentationthe description is "Retrieves full documentation content for Svelte 5 or SvelteK…"
- warnTC06list-sectionsthe description is "Lists all available Svelte 5 and SvelteKit documentation sec…"
- warnTC06playground-linkthe description is "Generates a Playground link given a Svelte code snippet. Onc…"
- warnTC11svelte-autofixer1 parameter without a description: code
- noteTC24server2 of 4 tools have no outputSchema
The checks from /check and anchor check, run each day on the list above: about 6,155 tokens of definitions. Not part of the score yet. Check your own server.