Svelte MCP: official docs and autofixes in your coding assistant

How to connect the Svelte MCP server to Cursor or Claude Code

1. 1Click Connect Svelte free. There's no sign-in, so its tools are ready at once.
2. 2All four tools are on once you connect. Docs lookups and autofixing both earn their place while you code; switch off `svelte-autofixer` if you'd rather your AI app work from the docs alone, or `playground-link` if snippets shouldn't leave your editor.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4In Cursor, ask your AI app to write a Svelte component with a reactive counter and run it past `svelte-autofixer`, then open Activity to see the calls.

Svelte development with your AI app

• Look up Svelte 5 and SvelteKit docs with `list-sections` and `get-documentation` without leaving your editor.
• Have `svelte-autofixer` check a component your AI app just wrote and suggest fixes.
• Get a Playground link for a snippet so you can try the code before it goes into your project.
• Ask why a Svelte component isn't behaving as expected and get an answer based on the docs.

One connection, every call recorded

• Svelte's server sits next to your other connections behind the single ContextGate connection in Cursor or Claude Code.
• Activity records each docs lookup and autofix call.
• Switch off a Svelte tool and Cursor or Claude Code stops seeing it; calls to it are refused.

What you get with Svelte and ContextGate

• Your AI apps can use SvelteClaude, Cursor, ChatGPT and other AI apps reach Svelte through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Svelte tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Svelte tools

Examples of what your AI apps can do in Svelte. You'll see the exact list of tools after you connect it.

• get-documentationRetrieves 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
• list-sectionsLists 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")
• playground-linkGenerates 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 impor
• svelte-autofixerGiven 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