Developer Tools
svelte.dev
Provides Svelte documentation retrieval, code analysis, and playground generation for developers.
ENDPOINT 1
https://mcp.svelte.dev/mcp
MCP server metadata
- Name
- Svelte MCP
- Version
- 0.0.1
This is the official Svelte MCP server. It MUST be used whenever svelte development is involved. It can provide official documentation, code examples and correct your code. After you correct the component call this tool again to confirm all the issues are fixed.
Known tools 4
get-documentationRetrieves full documentation content for Svelte 5 or SvelteKit sections.
Inferred read-onlylist-sectionsLists all available Svelte 5 and SvelteKit documentation sections in a structured format.
Inferred read-onlysvelte-autofixerGiven a svelte component or module returns a list of suggestions to fix any issues it has.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.svelte-mcp]
url = "https://mcp.svelte.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"svelte-mcp": {
"type": "http",
"url": "https://mcp.svelte.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: svelte-mcp
Remote MCP URL: https://mcp.svelte.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"svelte-mcp": {
"url": "https://mcp.svelte.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"svelte-mcp": {
"type": "http",
"url": "https://mcp.svelte.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "svelte-mcp",
"transport": "streamable-http",
"url": "https://mcp.svelte.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.