Svelte MCP server

• get-documentationFree

  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-sectionsFree

  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.

• playground-linkFree

  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-autofixerFree

  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

• Code scan3 source files scanned25/25
• Live reliabilityremote reachable in 684ms20/20
• Tool poisoning4 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 0 days ago15/15
• Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10

Svelte MCP: common questions

Is Svelte MCP server safe?

Yes, by our scan: it is graded A (93/100). Read the Svelte MCP safety report

How do I install Svelte MCP?

It runs remotely at mcp.svelte.dev. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Svelte MCP need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Svelte MCP maintained?

The last commit was in the last day (2026-09-23). The latest release is v0.1.26.

Is Svelte MCP up?

100% of our last 20 checks got an answer. We check remote servers about four times a day.

What can I use instead of Svelte MCP?

Servers from other publishers that do the same job: SvGrid MCP server, Context7 MCP server and Coolify MCP server. Compare all Svelte MCP alternatives.