Svelte MCP

REMOTE · MCP.SVELTE.DEV · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · mcp.svelte.dev 72 npm · @sveltejs/mcp 46

+5 this week 72 72 Trust /100

Trust breakdown (6 categories)

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 →

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 Usability64

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (poor).Fail
Tool/resource definitions use about 6849 tokens (~34/item across 201 items; 4 tools + 197 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities73

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Supports UI / widget rendering.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.svelte.dev

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http dev-svelte-mcp https://mcp.svelte.dev/mcp

# ~/.codex/config.toml

[mcp_servers.dev-svelte-mcp]
url = "https://mcp.svelte.dev/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-svelte-mcp": {
      "type": "remote",
      "url": "https://mcp.svelte.dev/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add dev-svelte-mcp --url https://mcp.svelte.dev/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  dev-svelte-mcp:
    url: "https://mcp.svelte.dev/mcp"

// mcp.json

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 64

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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=YR1,O=Let's Encrypt,C=US	26 Jul 2026	24 Oct 2026	RSA 2048	SHA256-RSA	61c8ade2da4fa8d56f74ec8020d01b38132
SANs: mcp.svelte.dev
CN=YR1,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	a20253f15f2691c05dc1ce13b9bcca4e
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

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

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

MCP tools — 4 exposed · ~918 tokens

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.

Tool Tokens

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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 ~241

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

Input Output Examples

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 major svelte version as an integer (must be 4 or 5)...if possible read this from the package.json of the user project, otherwise use some hint from the wording (if the user asks for runes…
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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	64
27 Jul	67
28 Jul	68
29 Jul	68
30 Jul	69
31 Jul	71
1 Aug	71
2 Aug	72
3 Aug	72