Installation

TypingMindClaude DesktopCursorVS CodeClaude CodeGemini CLICodexWindsurf

TypingMind

Copy

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

Available Tools

• 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 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.

• list-sections

  $2e

• playground-link

  Generates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code in the playground before calling this tool. NEVER use this tool if you have written the component to a file in the user project. The playground accept multiple files so if are importing from other files just include them all at the root level.

• 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