Svelte MCP
Svelte's official MCP server and plugin: current docs, component autofixing and Svelte 5 skills
Install
/plugin marketplace add sveltejs/ai-tools
/plugin install svelteLocal MCP server, skills and an agent for .svelte files.
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 autofixerLimitations
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.
MCP
- Transport
- stdio, http
- Authentication
- not required
Security check
- The remote version receives code snippets for analysis
- Runs a package from npm
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.
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.
Related
Official shadcn/ui skill and MCP server: the agent searches registries, adds components via the CLI and follows the library's rules
A frontend design skill with 23 commands, live browser iteration and 61 detector rules for common AI-generated UI tells
Vercel Agent Skills
Agent Skills
Vercel's skills: React and Next.js performance, UI guideline audits, React Native, component composition and deploys
An MCP server that gives the agent simplified Figma layout data from a link so it can build the screen more accurately than from a screenshot