Svelte MCP
REMOTE · MCP.SVELTE.DEV · 2 COMPONENTS
The official Svelte MCP server providing docs and autofixing tools for Svelte development
Available components
Last scanned (18 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 6982 tokens (~33/item across 208 items; 4 tools + 204 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +1
- “svelte-autofixer” reworded the description of “desired_svelte_version” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 10 Oct 26 0
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- New resource “kit/@sveltejs-kit-env” functional
- New resource “kit/adapter-cloudflare” functional
- New resource “svelte/getting-started” functional
- New resource “svelte/legacy-overview” functional
- New resource “kit/$lib” functional
- New resource “svelte/svelte-server” functional
- New resource “kit/@sveltejs-kit” functional
- New resource “svelte/browser-support” functional
- New resource “ai/prompts” functional
- New resource “kit/$app-paths” functional
- New resource “cli/storybook” functional
- New resource “ai/cursor-plugin” functional
- New resource “svelte/@render” functional
- New resource “svelte/legacy-svelte-self” functional
- New resource “svelte/scoped-styles” functional
- New resource “svelte/testing” functional
- New resource “svelte/svelte-reactivity” functional
- New resource “svelte/legacy-export-let” functional
- New resource “svelte/basic-markup” functional
- New resource “ai/copilot-plugin” functional
- New resource “kit/$app-manifest” functional
- New resource “cli/community” functional
- New resource “kit/$env-dynamic-private” functional
- New resource “cli/ai-tools” functional
- New resource “cli/vitest” functional
- New resource “cli/enhanced-img” functional
- New resource “kit/environment-variables” functional
- New resource “svelte/key” functional
- New resource “cli/paraglide” functional
- New resource “svelte/svelte-document” functional
- New resource “cli/sv-migrate” functional
- New resource “svelte/svelte-action” functional
- New resource “kit/$app-env-public” functional
- New resource “kit/integrations” functional
- New resource “cli/faq” functional
- New resource “ai/mcp” functional
- New resource “svelte/svelte-attachments” functional
- New resource “svelte/@attach” functional
- New resource “svelte/legacy-on” functional
- New resource “svelte/svelte-legacy” functional
- New resource “cli/mdsvex” functional
- New resource “kit/@sveltejs-kit-adapter” functional
- New resource “kit/$app-env-private” functional
- New resource “kit/types” functional
- New resource “kit/writing-adapters” functional
- New resource “kit/adapter-auto” functional
- New resource “kit/$env-static-private” functional
- New resource “svelte/$props” functional
- New resource “kit/state-management” functional
- New resource “svelte/legacy-slots” functional
- New resource “kit/form-actions” functional
- New resource “svelte/await” functional
- New resource “kit/@sveltejs-kit-hooks” functional
- New resource “svelte/nested-style-elements” functional
- New resource “kit/introduction” functional
- New resource “svelte/typescript” functional
- New resource “kit/$app-navigation” functional
- New resource “kit/project-structure” functional
- New resource “kit/images” functional
- New resource “svelte/@html” functional
- New resource “kit/observability” functional
- New resource “svelte/svelte-js-files” functional
- New resource “ai/instructions” functional
- New resource “svelte/runtime-errors” functional
- New resource “cli/sv-utils” functional
- New resource “cli/eslint” functional
- New resource “cli/prettier” functional
- New resource “kit/@sveltejs-kit-params” functional
- New resource “svelte/$effect” functional
- New resource “svelte/hydratable” functional
- New resource “svelte/svelte-window” functional
- New resource “svelte/legacy-$$props-and-$$restProps” functional
- New resource “svelte/$derived” functional
- New resource “ai/resources” functional
- New resource “kit/page-options” functional
- New resource “kit/debugging” functional
- New resource “svelte/svelte-events” functional
- New resource “ai/remote-setup” functional
- New resource “kit/faq” functional
- New resource “cli/sveltekit-adapter” functional
- New resource “kit/link-options” functional
- New resource “svelte/svelte-body” functional
- New resource “kit/icons” functional
- New resource “ai/opencode-plugin” functional
- New resource “kit/$app-tsconfig-service-worker” functional
- New resource “svelte/legacy-svelte-fragment” functional
- New resource “kit/$app-forms” functional
- New resource “svelte/svelte-head” functional
- New resource “svelte/animate” functional
- New resource “kit/migrating” functional
- New resource “kit/adapter-vercel” functional
- New resource “kit/performance” functional
- New resource “svelte/lifecycle-hooks” functional
- New resource “ai/codex-plugin” functional
- New resource “ai/subagent” functional
- New resource “svelte/legacy-component-api” functional
- New resource “svelte/if” functional
- New resource “kit/glossary” functional
- New resource “svelte/stores” functional
- New resource “kit/snapshots” functional
- New resource “svelte/what-are-runes” functional
- New resource “kit/seo” functional
- New resource “svelte/legacy-$$slots” functional
- New resource “svelte/svelte-easing” functional
- New resource “kit/creating-a-project” functional
- New resource “svelte/snippet” functional
- New resource “svelte/use” functional
- New resource “svelte/$host” functional
- New resource “ai/claude-plugin” functional
- New resource “cli/sv-check” functional
- New resource “kit/cli” functional
- New resource “svelte/declaration-tags” functional
- New resource “ai/skills” functional
- New resource “kit/single-page-apps” functional
- New resource “svelte/v5-migration-guide” functional
- New resource “svelte/$bindable” functional
- New resource “cli/drizzle” functional
- New resource “kit/adapter-static” functional
- New resource “svelte/transition” functional
- New resource “kit/migrating-to-sveltekit-3” functional
- New resource “kit/errors” functional
- New resource “svelte/imperative-component-api” functional
- New resource “kit/adapter-cloudflare-workers” functional
- New resource “cli/sv” functional
- New resource “svelte/svelte-store” functional
- New resource “svelte/svelte-options” functional
- New resource “cli/sv-add” functional
- New resource “kit/accessibility” functional
- New resource “svelte/legacy-svelte-component” functional
- New resource “kit/@sveltejs-kit-node” functional
- New resource “svelte/in-and-out” functional
- New resource “svelte/compiler-errors” functional
- New resource “kit/$app-environment” functional
- New resource “svelte/@const” functional
- New resource “cli/sv-create” functional
- New resource “svelte/runtime-warnings” functional
- New resource “kit/remote-functions” functional
- New resource “svelte/context” functional
- New resource “svelte/best-practices” functional
- New resource “kit/$app-types” functional
- New resource “kit/$service-worker” functional
- New resource “svelte/svelte-transition” functional
- New resource “kit/@sveltejs-kit-vite” functional
- New resource “svelte/class” functional
- New resource “kit/adapters” functional
- New resource “svelte/svelte-element” functional
- New resource “kit/adapter-netlify” functional
- New resource “kit/$app-service-worker” functional
- New resource “ai/cli” functional
- New resource “kit/auth” functional
- New resource “kit/service-workers” functional
- New resource “kit/building-your-app” functional
- New resource “kit/adapter-node” functional
- New resource “cli/overview” functional
- New resource “svelte/svelte-animate” functional
- New resource “kit/additional-resources” functional
- New resource “kit/shallow-routing” functional
- New resource “ai/overview” functional
- New resource “svelte/overview” functional
- New resource “svelte/legacy-let” functional
- New resource “cli/tailwind” functional
- New resource “svelte/custom-elements” functional
- New resource “svelte/global-styles” functional
- New resource “kit/project-types” functional
- New resource “svelte/legacy-reactive-assignments” functional
- New resource “kit/adapter-bun” functional
- New resource “kit/packaging” functional
- New resource “kit/migrating-to-sveltekit-2” functional
- New resource “svelte/svelte” functional
- New resource “cli/better-auth” functional
- New resource “svelte/faq” functional
- New resource “svelte/compiler-warnings” functional
- New resource “kit/advanced-routing” functional
- New resource “ai/tools” functional
- New resource “svelte/svelte-boundary” functional
- New resource “kit/hooks” functional
- New resource “svelte/svelte-motion” functional
- New resource “svelte/bind” functional
- New resource “kit/$app-tsconfig” functional
- New resource “svelte/custom-properties” functional
- New resource “svelte/svelte-compiler” functional
- New resource “ai/local-setup” functional
- New resource “kit/$app-server” functional
- New resource “kit/web-standards” functional
- New resource “kit/$env-dynamic-public” functional
- New resource “kit/$app-stores” functional
- New resource “cli/playwright” functional
- New resource “svelte/svelte-reactivity-window” functional
- New resource “svelte/$inspect” functional
- New resource “svelte/v4-migration-guide” functional
- New resource “kit/$app-env” functional
- New resource “cli/experimental” functional
- New resource “svelte/svelte-files” functional
- New resource “svelte/@debug” functional
- New resource “svelte/$state” functional
- New resource “kit/load” functional
- New resource “svelte/style” functional
- New resource “kit/$env-static-public” functional
- 4 Oct 26 +1
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- 3 Oct 26 −1
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- 11 Sept 26 88
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://mcp.svelte.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.svelte.dev | CN=YR2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 509525ced3a2e72ed579f4ec5fb9721d5dd |
| SANs: mcp.svelte.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.svelte.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| svelte.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.svelte.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.svelte.dev/mcp | HTTPS enforced | 308 | https://mcp.svelte.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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… ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| section | – | yes | The section name(s) to retrieve. Can search by title (e.g., "$state", "load functions") or file path (e.g., "cli/overview"). Supports single string and array of strings |
No output schema declared.
No examples provided.
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… ~244
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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 qui… ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | object | yes | An object where all the keys are the filenames (with extensions) and the values are the file content. For example: { 'Component.svelte': '<script>...</script>', 'utils.js': 'export function ...' }. T… |
| name | string | yes | The name of the Playground, it should reflect the user task |
| tailwind | boolean | yes | If the code requires Tailwind CSS to work...only send true if it it's using tailwind classes in the code |
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No examples provided.
svelte-autofixer Svelte Autofixer ~286
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
| Name | Type | Req | Description |
|---|---|---|---|
| async | boolean | – | If true the code is an async component/module and might use await in the markup or top-level awaits in the script tag. If possible check the svelte.config.js/svelte.config.ts to check if the option i… |
| code | string | yes | – |
| desired_svelte_version | – | yes | The desired svelte version as a full semver string (e.g. "5.16.0", the major MUST be 4 or 5)...you MUST read this from the package.json of the user project (or from the installed node_modules/svelte/… |
| filename | string | – | The filename of the component if available, it MUST be only the Component name with .svelte or .svelte.ts extension and not the entire path. |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | yes | – |
| require_another_tool_call_after_fixing | boolean | yes | – |
| suggestions | array | yes | – |
No examples provided.
How do I install the Svelte MCP server?
Svelte MCP is a hosted endpoint at https://mcp.svelte.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.svelte.dev
claude mcp add --transport http dev-svelte-mcp 'https://mcp.svelte.dev/mcp'
What is the Svelte MCP server?
Svelte MCP is listed in the public MCP registry as dev.svelte/mcp. The official Svelte MCP server providing docs and autofixing tools for Svelte development. This page covers its hosted endpoint (https://mcp.svelte.dev/mcp).
Is the Svelte MCP server safe to use?
Svelte MCP scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Svelte MCP server expose?
Svelte MCP exposes 4 tools: get-documentation, list-sections, playground-link, svelte-autofixer. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.
Does the Svelte MCP server require authentication?
No. We connected to Svelte MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Svelte MCP server still maintained?
Svelte MCP is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.