bots.st/svelte-mcp
Svelte MCP
Fetch Svelte docs, suggest autofixes
1903 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 4
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.svelte.dev/mcp - npm
npx -y @sveltejs/mcpReleased 4 Nov 2026, version 0.1.30
What it can do
| Tool | What it says it does |
|---|---|
get-documentation | 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 sections. Before running this, make sure to analyze the users query, as well… |
list-sections | 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 the use_cases field to determine which sections are relevant for the user's… |
playground-link | 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 in the playground before calling this tool. NEVER use this tool if you have… |
svelte-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 |
In its maker's words
The official Svelte MCP server providing docs and autofixing tools for Svelte development
- Website
- svelte.dev/docs/mcp/overview
- Source
- github.com/sveltejs/ai-tools
- Publisher
- svelte.dev
- Listed from
- the official MCP Registry as
dev.svelte/mcp - Version
- 0.1.30, updated 4 Nov 2026
- Kinds of work
- Writing and translation, Documents and files, Browser and automation
The domain it lives on
- svelte.dev
- registered 28 Feb 2019 (7 years ago), at CloudFlare, Inc., its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1903 ms | |
| Answered | 1856 ms | |
| Answered | 318 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.