{
"generatedAt": "2026-09-09T20:58:37.774Z",
"id": "svelte",
"name": "Svelte",
"url": "https://mcp.svelte.dev/mcp",
"homepage": "https://svelte.dev/docs/mcp",
"platform": null,
"transport": "streamable-http",
"status": "ok",
"error": null,
"protocolVersion": null,
"serverInfo": null,
"provenance": {
"at": "2026-09-09T20:58:37.774Z",
"declaredUrl": "https://mcp.svelte.dev/mcp",
"observedUrl": "https://mcp.svelte.dev/mcp",
"urlMatchesDeclared": true,
"redirected": false,
"redirects": [],
"via": "direct-post",
"envelope": "sse",
"methodChangingRedirect": false,
"refused": null
},
"tools": [
{
"name": "get-documentation",
"title": "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.",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"section": {
"anyOf": [
{
"type": "string"
},
{
"type": "array",
"items": {
"type": "string"
}
}
],
"description": "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"
}
},
"required": [
"section"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"outputSchema": null,
"annotations": {
"title": "Get Documentation",
"destructiveHint": false,
"readOnlyHint": true,
"openWorldHint": false
},
"schemaFingerprint": "edc02b5153b29bba"
},
{
"name": "list-sections",
"title": "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.",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"outputSchema": null,
"annotations": {
"title": "List Sections",
"destructiveHint": false,
"readOnlyHint": true,
"openWorldHint": false
},
"schemaFingerprint": "efddc7bd8bbcef73"
},
{
"name": "playground-link",
"title": "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.",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "The name of the Playground, it should reflect the user task"
},
"tailwind": {
"type": "boolean",
"description": "If the code requires Tailwind CSS to work...only send true if it it's using tailwind classes in the code"
},
"files": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "string"
},
"description": "An object where all the keys are the filenames (with extensions) and the values are the file content. For example: { 'Component.svelte': '', 'utils.js': 'export function ...' }. The playground accept multiple files so if are importing from other files just include them all at the root level."
}
},
"required": [
"name",
"tailwind",
"files"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"outputSchema": {
"type": "object",
"properties": {
"url": {
"type": "string"
}
},
"required": [
"url"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"annotations": {
"title": "Playground Link",
"destructiveHint": false,
"readOnlyHint": true,
"openWorldHint": false
},
"schemaFingerprint": "64fac85cbd6f310d"
},
{
"name": "svelte-autofixer",
"title": "Svelte Autofixer",
"description": "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",
"inputSchema": {
"type": "object",
"properties": {
"code": {
"type": "string"
},
"desired_svelte_version": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
}
],
"description": "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 it wants version 5). Default to 5 in case of doubt."
},
"async": {
"type": "boolean",
"description": "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 is enabled otherwise asks the user if they prefer using it or not. You can only use this option if the version is 5."
},
"filename": {
"type": "string",
"description": "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."
}
},
"required": [
"code",
"desired_svelte_version"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"outputSchema": {
"type": "object",
"properties": {
"issues": {
"type": "array",
"items": {
"type": "string"
}
},
"suggestions": {
"type": "array",
"items": {
"type": "string"
}
},
"require_another_tool_call_after_fixing": {
"type": "boolean"
}
},
"required": [
"issues",
"suggestions",
"require_another_tool_call_after_fixing"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"annotations": {
"title": "Svelte Autofixer",
"destructiveHint": false,
"readOnlyHint": true,
"openWorldHint": false
},
"schemaFingerprint": "58985309594bfa21"
}
],
"toolCount": 4,
"fingerprint": "186bae06bc1b96ee",
"lastGood": {
"at": "2026-09-09T20:58:37.774Z",
"tools": [
{
"name": "get-documentation",
"title": "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.",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"section": {
"anyOf": [
{
"type": "string"
},
{
"type": "array",
"items": {
"type": "string"
}
}
],
"description": "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"
}
},
"required": [
"section"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"outputSchema": null,
"annotations": {
"title": "Get Documentation",
"destructiveHint": false,
"readOnlyHint": true,
"openWorldHint": false
},
"schemaFingerprint": "edc02b5153b29bba"
},
{
"name": "list-sections",
"title": "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.",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"outputSchema": null,
"annotations": {
"title": "List Sections",
"destructiveHint": false,
"readOnlyHint": true,
"openWorldHint": false
},
"schemaFingerprint": "efddc7bd8bbcef73"
},
{
"name": "playground-link",
"title": "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.",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "The name of the Playground, it should reflect the user task"
},
"tailwind": {
"type": "boolean",
"description": "If the code requires Tailwind CSS to work...only send true if it it's using tailwind classes in the code"
},
"files": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {
"type": "string"
},
"description": "An object where all the keys are the filenames (with extensions) and the values are the file content. For example: { 'Component.svelte': '', 'utils.js': 'export function ...' }. The playground accept multiple files so if are importing from other files just include them all at the root level."
}
},
"required": [
"name",
"tailwind",
"files"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"outputSchema": {
"type": "object",
"properties": {
"url": {
"type": "string"
}
},
"required": [
"url"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"annotations": {
"title": "Playground Link",
"destructiveHint": false,
"readOnlyHint": true,
"openWorldHint": false
},
"schemaFingerprint": "64fac85cbd6f310d"
},
{
"name": "svelte-autofixer",
"title": "Svelte Autofixer",
"description": "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",
"inputSchema": {
"type": "object",
"properties": {
"code": {
"type": "string"
},
"desired_svelte_version": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
}
],
"description": "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 it wants version 5). Default to 5 in case of doubt."
},
"async": {
"type": "boolean",
"description": "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 is enabled otherwise asks the user if they prefer using it or not. You can only use this option if the version is 5."
},
"filename": {
"type": "string",
"description": "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."
}
},
"required": [
"code",
"desired_svelte_version"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"outputSchema": {
"type": "object",
"properties": {
"issues": {
"type": "array",
"items": {
"type": "string"
}
},
"suggestions": {
"type": "array",
"items": {
"type": "string"
}
},
"require_another_tool_call_after_fixing": {
"type": "boolean"
}
},
"required": [
"issues",
"suggestions",
"require_another_tool_call_after_fixing"
],
"$schema": "http://json-schema.org/draft-07/schema#"
},
"annotations": {
"title": "Svelte Autofixer",
"destructiveHint": false,
"readOnlyHint": true,
"openWorldHint": false
},
"schemaFingerprint": "58985309594bfa21"
}
],
"fingerprint": "186bae06bc1b96ee",
"protocolVersion": null
},
"firstSeenAt": "2026-09-09T10:24:48.004Z",
"lastCheckedAt": "2026-09-09T20:58:37.774Z",
"lastOkAt": "2026-09-09T20:58:37.774Z",
"lastChangedAt": null,
"changeCount": 0,
"card": {
"id": "svelte",
"cardUrl": "https://mcp.svelte.dev/.well-known/mcp/server-card.json",
"at": "2026-09-09T20:58:37.774Z",
"cardPath": "/.well-known/mcp/server-card.json",
"status": "not_json",
"error": "Unexpected token '<', \"