OfficialDev & code hostinglocal stdio / remote HTTP

Svelte MCP

Gives agents the current Svelte docs plus a static-analysis autofixer for generated Svelte code.

Install

Claude Code

(local; [scope] must be user, project or local)

claude mcp add -t stdio -s [scope] svelte -- npx -y @sveltejs/mcp

Claude Code

(remote)

claude mcp add -t http -s [scope] svelte https://mcp.svelte.dev/mcp

The docs also offer a svelte plugin in the Svelte Claude Code Marketplace that configures the local server together with skills.

Codex CLI

(local, in ~/.codex/config.toml; the docs recommend the Codex plugin for automatic setup)

[mcp_servers.svelte]
command = "npx"
args = ["-y", "@sveltejs/mcp"]

Codex CLI

(remote, in ~/.codex/config.toml)

experimental_use_rmcp_client = true
[mcp_servers.svelte]
url = "https://mcp.svelte.dev/mcp"

Cursor

(View: Open MCP Settings → Add custom MCP; local)

{
	"mcpServers": {
		"svelte": {
			"command": "npx",
			"args": ["-y", "@sveltejs/mcp"]
		}
	}
}

Cursor

(remote)

{
	"mcpServers": {
		"svelte": {
			"url": "https://mcp.svelte.dev/mcp"
		}
	}
}

Copilot CLI

run /mcp add, or add to ~/.copilot/mcp-config.json (remote shown; for local use the npx block above)

{
	"mcpServers": {
		"svelte": {
			"url": "https://mcp.svelte.dev/mcp"
		}
	}
}

VS Code

Command Palette → MCP: Add Server... → Command (stdio), enter npx -y @sveltejs/mcp, name it svelte, then choose Global or Workspace.

Antigravity CLI

(~/.gemini/config/mcp_config.json, local)

{
	"mcpServers": {
		"svelte": {
			"command": "npx",
			"args": ["-y", "@sveltejs/mcp"]
		}
	}
}

Claude Desktop

(remote): Settings → Connectors → Add Custom Connector, name svelte, URL https://mcp.svelte.dev/mcp.

Commands and configuration as given in the Svelte docs for the local and remote server.

Svelte MCP is the Svelte team’s official server for current Svelte docs and code checks in coding agents.

The Svelte MCP server gives an agent the official Svelte documentation and a static-analysis checker for the Svelte code it writes. The Svelte team maintains it in the sveltejs/ai-tools repository under the MIT license. It runs locally over stdio as the @sveltejs/mcp package through npx, or remotely at https://mcp.svelte.dev/mcp; neither needs an API key (local setup, remote setup). This listing reflects @sveltejs/mcp version 0.1.26 in the repository’s package.json.

It has four tools (Svelte docs, Tools). list-sections lists the available documentation sections and get-documentation returns the full, current text of the requested sections from svelte.dev/docs. svelte-autofixer runs static analysis on generated code and returns suggestions; the model can call it in a loop until no issues are left. playground-link creates an ephemeral Svelte Playground link with the code, which is stored only in the URL itself.

For the remote server, the docs say the Svelte team does not log, store or inspect code sent to it (remote setup). The same docs also cover a short instructions prompt, agent skills and subagents that work alongside the server (overview).

Questions

Is the Svelte MCP server official?
Yes. The Svelte docs describe it as one of the AI tools officially maintained by the Svelte team, and the source is in the sveltejs/ai-tools repository.
Do I need an API key for Svelte MCP?
No. The local server runs through npx -y @sveltejs/mcp, and the remote one is a plain URL, https://mcp.svelte.dev/mcp, with no key in either setup.
Local or remote: which should I use?
Local runs on your machine through npx; remote needs no install. For the remote server, the Svelte team says it does not log, store or inspect code sent to it.
What does svelte-autofixer do?
It runs static analysis on Svelte code the model generates and returns issues and suggestions. The model can call it repeatedly until everything is resolved.

Sources

Checked October 5, 2026.

Dev & code hosting

View all
Aftergradient

What are you looking for?

Search commands, errors, tools