Svelte is a remote MCP server that gives an AI agent 4 tools, among them get-documentation, list-sections, playground-link. It answers at https://mcp.svelte.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
The official Svelte MCP server providing docs and autofixing tools for Svelte development
Description as the publisher wrote it.
| Tool | What 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 run Inputs: section |
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 |
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 bef Inputs: name, tailwind, files |
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 Inputs: code, desired_svelte_version, async, filename |
Every block below points at https://mcp.svelte.dev/mcp. Pick your client and copy.
claude mcp add --transport http svelte https://mcp.svelte.dev/mcp
{
"mcpServers": {
"svelte": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.svelte.dev/mcp"]
}
}
}{
"mcpServers": {
"svelte": {
"url": "https://mcp.svelte.dev/mcp"
}
}
}{
"servers": {
"svelte": {
"type": "http",
"url": "https://mcp.svelte.dev/mcp"
}
}
}{
"context_servers": {
"svelte": {
"url": "https://mcp.svelte.dev/mcp"
}
}
}{
"mcpServers": {
"svelte": {
"serverUrl": "https://mcp.svelte.dev/mcp"
}
}
}{
"mcpServers": {
"svelte": {
"url": "https://mcp.svelte.dev/mcp"
}
}
}name: Svelte
version: 0.0.1
schema: v1
mcpServers:
- name: Svelte
type: streamable-http
url: https://mcp.svelte.dev/mcp{
"mcpServers": {
"svelte": {
"httpUrl": "https://mcp.svelte.dev/mcp"
}
}
}{
"mcpServers": {
"svelte": {
"type": "http",
"url": "https://mcp.svelte.dev/mcp"
}
}
}{
"mcpServers": {
"svelte": {
"url": "https://mcp.svelte.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.svelte.dev%2Fmcp&type=streamable_http&id=svelte&name=Svelte
It answered our last check on 19 October 2026 in 357 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by svelte.dev and served from mcp.svelte.dev, the vendor's own domain: https://mcp.svelte.dev/mcp.
4, as returned by the server's own tools/list on 11 September 2026: get-documentation, list-sections, playground-link, svelte-autofixer.
It answered our last check on 19 October 2026 in 357 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.svelte.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.svelte. Endpoint host: mcp.svelte.dev. ARD identifier: urn:air:dev.svelte:mcp:mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.