Svelte MCP

dev.sveltePublished by svelte.devOfficial publisherv0.1.30Updated Nov 5, 2026

The official Svelte MCP server providing docs and autofixing tools for Svelte development

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Official Svelte MCP server that gives an assistant Svelte 5 and SvelteKit documentation lookup, code autofixing suggestions, and Playground links.

What you can do
  • List and retrieve Svelte 5 and SvelteKit documentation sections by title or file path, including use-case hints for picking the right section
  • Review Svelte components or modules and get a list of suggested fixes for issues found
  • Generate a Svelte Playground link from a code snippet so the user can try it in the browser
When to use it
Useful when an assistant writes, reviews or debugs Svelte 5 or SvelteKit code and should ground answers in official docs and check components before returning them.
Requirements
Runs as a remote endpoint at mcp.svelte.dev, or locally via npx @sveltejs/mcp (Node.js) or an installed package. No authentication, environment variables or headers are declared.
Before you install
The server's instructions push assistants to use it for all Svelte work and to re-run the autofixer after fixes; treat that as guidance, not a rule. Playground links send the code snippet to Svelte's Playground service, so avoid snippets containing secrets or private code.

Installation

In SourceWeft

  1. Open Svelte MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.svelte%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

@sveltejs/mcp

The CLI version of the Svelte MCP.

You can run it directly with

bash
npx @sveltejs/mcp

or install it and then run it

bash
pnpm i @sveltejs/mcppnpm svelte-mcp

Source: packages/mcp-stdio/README.md at commit a5a92c6

Tools

4

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 running this, make sure to analyze the users query, as well as the output from list-sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to f

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 running this, make sure to analyze the users query, as well as the output from list-sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to fetch all relevant runes, and so on. Before calling this tool, try to implement Svelte components using your own knowledge and the `svelte-autofixer` tool, since calling this tool is token intensive.

Parameterssectionrequired

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 determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stag

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 determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get-documentation to fetch ALL relevant sections at once.

Takes no parameters.

svelte-autofixer

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

Parameterscoderequiredasyncfilenamedesired_svelte_versionrequired

Version history

4
  1. v0.1.30LatestNov 4, 2026
  2. v0.1.28Oct 26, 2026
  3. v0.1.27Oct 19, 2026
  4. v0.1.26Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts