Svelte MCP
Svelte's official MCP server and plugin: current docs, component autofixing and Svelte 5 skills
- 335 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The remote version receives code snippets for analysis
- Runs a package from npm
Install
- Works in
Manual install
/plugin marketplace add sveltejs/ai-tools
/plugin install svelteLocal MCP server, skills and an agent for .svelte files.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The remote version receives code snippets for analysis
- Runs a package from npm
This is third-party code. Review the repository files before installing.
What it does
The server gives an agent the official Svelte docs by section so it stops writing code from stale knowledge. The svelte-autofixer tool checks generated code with static analysis and returns suggestions, and the agent can loop on it until none remain. The playground-link tool builds a playground link with the code for a quick check. The repository is also a plugin marketplace: the svelte plugin for Claude Code installs the local server, Svelte 5 skills and a dedicated agent for editing .svelte files.
Who it is for. For frontend developers building with Svelte and SvelteKit alongside an agent.
Good fit when
- The agent mixes up Svelte 4 and Svelte 5 syntax
- You want to check a generated component before writing it to the project
- You want to share a code sample in the Svelte playground
Not a fit when
- The project does not use Svelte
- Code must not leave the machine and you cannot run the local version
Example request
Build a Svelte 5 cart component with runes and check it with the autofixerMCP
- Transport
- stdio, http
- Authentication
- not required
Limitations
The repository README covers only development; install instructions live in the svelte.dev docs. The remote server calls mcp.svelte.dev, and the Svelte team states it does not store or inspect submitted code. The local version runs through npx without keys.
How to disable. Run claude mcp remove svelte or uninstall the svelte plugin via /plugin. In other clients remove the svelte block from config.
FAQ
Plugin, local or remote server?
The Claude Code plugin bundles the server with skills and an agent. The local npx server keeps code on your machine. The remote one needs no Node.js and connects at https://mcp.svelte.dev/mcp.
Was the repository renamed?
Yes, it used to be sveltejs/mcp; it now holds the server, skills and plugins.
Discussion
No questions or reviews yet.
Related
MCP serversNuxt MCP Dev
nuxt-mcp-dev / vite-plugin-mcp
A Nuxt module and a Vite plugin start an MCP server on the dev server port so the agent sees config, pages, components, auto-imports and the module graph
A visual website builder with a built-in MCP server: the agent helps assemble static pages with dynamic data on the model you choose
21st.dev MCP server and plugin: search ready React/Tailwind components and logos and generate UI from your agent
Shadcn UI MCP Server
Shadcn UI v4 MCP Server
An MCP server that gives the agent shadcn/ui component source, demos and blocks for React, Svelte, Vue and React Native
Connects an agent to a running Next.js 16+ dev server: errors, routes, logs and docs for your installed version
An MCP server plus a Chrome extension: pick a DOM element by Option-click and the agent gets its text, styles and selector
README in short
The README itself is short and covers only running the project for development and the inspectors. Installation, tools and client setup are in the AI section of svelte.dev: the local @sveltejs/mcp package, the remote URL, plugins for Claude Code, Codex and Copilot, skills and subagents. MIT licensed.