mcp-svelte-docs
MCP server giving an agent reference answers on Svelte 5 runes and SvelteKit: signatures, parameters and examples at three depths
- 124 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The single tool returns reference text for an identifier and takes no keys.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-svelte-docsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The single tool returns reference text for an identifier and takes no keys.
This is third-party code. Review the repository files before installing.
What it does
mcp-svelte-docs gives an agent a single tool, `svelte_definition(identifier, format)`. Given an identifier such as `$state`, `snippets` or `migration-patterns`, it returns a definition taken from the Svelte 5 TypeScript declarations. There are more than 28 identifiers: the `$state`, `$derived`, `$props` and `$effect` runes with their variants, snippets, events, global state, common mistakes and moving from Svelte 4 to Svelte 5. The `format` parameter sets the depth: `syntax` returns the signature, `quick` a definition with a short example, `full` the complete description with examples (the default). On a typo in the identifier the server hints at similar and related concepts.
Who it is for. Svelte 5 and SvelteKit developers who want their agent to check exact definitions.
Good fit when
- An agent writes a Svelte 5 component and checks the signatures of `$props` and `$bindable`.
- Svelte 4 code is being moved to runes and migration patterns are needed.
- A component mixes up `$effect`, `$effect.pre` and `$effect.root` and their definitions have to be compared.
- The agent needs a reference for `$app.state` or `$env.static.private` from SvelteKit.
- A compact reference is enough: the `syntax` format is about fifty words.
Not a fit when
- You need documentation for third-party Svelte libraries: the server knows only Svelte 5 and SvelteKit.
- The project stays on Svelte 4 without moving to runes.
- You need tutorials and guides: the server returns definitions only.
Example request
Show the `$derived.by` definition in full format and compare it with `$derived` so I can rewrite the computed value.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
The reference covers more than 28 Svelte 5 and SvelteKit identifiers; other topics are outside it. The typo hint uses fuzzy matching: an unknown identifier returns only a list of similar ones. The package is at version 0.0.22, the project is young and the identifier set keeps growing. For Claude Desktop and Windsurf on Windows the README shows a launch through `wsl.exe`, other clients need only `npx -y mcp-svelte-docs`. The server needs no keys or environment variables and runs locally over stdio.
How to disable. Remove the `mcp-svelte-docs` block from `mcpServers` in the client config and restart the client.
FAQ
Which response formats does `svelte_definition` have?
Three: `syntax` gives the TypeScript signature in about fifty words, `quick` a definition with an example in about two hundred, `full` a complete description in 500–1000 words. `full` is the default.
How do I connect the server to Cursor?
The README has an install button for Cursor. It adds the server with the command `npx -y mcp-svelte-docs`, the same as a manual config entry.
Are API keys needed?
No. The README lists no keys or environment variables: the command `npx -y mcp-svelte-docs` is enough.
What does the server return on a typo in the identifier?
A list of close identifiers and related concepts. The corrected name can go straight into a repeated call.
Which topics does the reference cover?
Svelte 5 runes, snippets, event handling, await expressions, remote functions, global state, common mistakes, migration from Svelte 4, the `Snippet` and `Snapshot` interfaces and SvelteKit modules such as `$app.state`.
Discussion
No questions or reviews yet.
Related
MCP serversSvelte's official MCP server and plugin: current docs, component autofixing and Svelte 5 skills
svelte-skills-kit is a Claude Code plugin marketplace with Svelte and SvelteKit skills and a language server for .svelte files.
The SvGrid MCP server checks agent code against the real SvGrid API and serves docs pinned to the installed version.
Skills for Claude Code on Svelte 5 and SvelteKit: runes, data loading, project structure, remote functions and deployment
shadcn-svelte skill for agents
shadcn-svelte
A shadcn-svelte skill: the agent reads components.json, adds components with the CLI and builds forms, dialogs and cards by the library's rules
Nuxt MCP Dev
nuxt-mcp-dev / vite-plugin-mcp
A Nuxt module and a Vite plugin start an MCP server on the dev server port so the agent sees config, pages, components, auto-imports and the module graph
README in short
The server builds its reference on definitions from the Svelte TypeScript declarations, so answers follow the current API. One tool replaces more than sixteen narrow tools of earlier versions.