MCP Svelte Docs Server
The MCP Svelte Docs Server provides comprehensive documentation and guidance for Svelte 5 and SvelteKit development through specialized tools.
Access detailed documentation for Svelte 5 core runes:
$state,$derived,$props, and$effectLearn about Svelte 5 features like snippets (replacing slots), event handling, component events, and global state management strategies
Explore modern async features including await expressions, boundaries, and SvelteKit remote functions for type-safe client-server communication
Get Svelte 4 to Svelte 5 migration guidance with searchable patterns using the
patternparameter for specific areas like "reactive", "props", or "events"Identify and avoid common mistakes in Svelte 5 development with filtering by categories such as "state", "props", or "events" using the
categoryparameterAccess comprehensive overviews of all Svelte 5 features and runes
Control documentation detail with the optional
includeExamplesparameter (defaults to true) to choose between documentation with or without code examples
Provides efficient access to Svelte documentation with advanced search capabilities, caching, and optimized content delivery. Supports package-specific documentation for Svelte, Kit, and CLI.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Svelte Docs Servershow me the syntax for $state"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-svelte-docs
A Model Context Protocol (MCP) server providing authoritative Svelte 5 and SvelteKit definitions extracted directly from TypeScript declarations. Get precise syntax, parameters, and examples for all Svelte 5 concepts through a single, unified interface.
Architecture
Definition-First Approach: Rather than multiple specialized tools,
this server provides one powerful svelte_definition tool that
accesses 28+ comprehensive definitions covering:
All Svelte 5 runes ($state, $derived, $props, $effect variants)
Modern features (snippets, await expressions, remote functions)
Event handling (DOM events, custom events, component communication)
Migration guidance (Svelte 4 to 5 patterns and best practices)
TypeScript interfaces (Snippet, Snapshot types)
Advanced patterns (global state, common mistakes, lifecycle equivalents)
Related MCP server: mcp-docs
Available Tool
svelte_definition
Single, powerful tool for all Svelte 5 and SvelteKit concepts:
svelte_definition(identifier: string, format?: "syntax"|"quick"|"full")Examples:
svelte_definition("$state")- Complete $state documentationsvelte_definition("snippets", "quick")- Snippet overview with examplesvelte_definition("onclick", "syntax")- Just the TypeScript signaturesvelte_definition("migration-patterns")- Svelte 4 → 5 migration guide
Response Formats:
"syntax"- TypeScript signature only (~50 words)"quick"- Definition + minimal example (~200 words)"full"- Complete documentation with examples (~500-1000 words, default)
Available Identifiers (28+)
Core Runes: $state, $state.raw, $state.snapshot, $derived,
$derived.by, $props, $bindable, $effect, $effect.pre,
$effect.root, $effect.pending, $effect.tracking
Development Tools: $inspect, $host
Features & Patterns: snippets, onclick, component-events,
migration-patterns, await-expressions, remote-functions,
global-state, common-mistakes, lifecycle-equivalents
Event Handling: custom-events, event-delegation,
event-modifiers
TypeScript Interfaces: snippet, snapshot
Key Features
🎯 Authoritative & TypeScript-First
Direct from Source: Definitions extracted from official Svelte 5 TypeScript declarations
Always Current: Reflects the actual API, not outdated tutorials
Type-Safe: Includes precise parameter types, return values, and constraints
⚡ Single Interface, Complete Coverage
One Tool:
svelte_definitionreplaces 16+ specialized tools28+ Definitions: Every Svelte 5 rune, feature, and pattern covered
Consistent Responses: Same interface whether you need
$stateorremote-functions
🚀 Modern Svelte 5 & SvelteKit Support
Await Expressions: Async operations directly in templates (
await-expressions)Remote Functions: Type-safe client-server communication (
remote-functions)All Runes: Complete
$effectfamily,$statevariants,$derived.by,$bindableAdvanced Patterns: Event handling, global state, component communication
📚 Smart Error Recovery
Fuzzy Matching: Suggests correct identifiers for typos
Related Concepts: Points to similar definitions when searches fail
Migration Help: Converts Svelte 4 patterns to Svelte 5 equivalents
Config
Claude Desktop (via WSL)
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "wsl.exe",
"args": ["bash", "-c", "npx -y mcp-svelte-docs"]
}
}
}Cursor
Windsurf (via WSL)
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "wsl.exe",
"args": ["bash", "-c", "npx -y mcp-svelte-docs"]
}
}
}Windows (without WSL)
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "npx",
"args": ["-y", "mcp-svelte-docs"]
}
}
}macOS / Linux
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "npx",
"args": ["-y", "mcp-svelte-docs"]
}
}
}Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT License - see the LICENSE file for details.
Acknowledgments
Built on:
Available Tools
1 toolsvelte_definitionLookup Svelte 5 & SvelteKit definitions from TypeScript declarations. Covers all runes ($state, $derived, $props, $effect), features (snippets, onclick, component-events), and patterns. Supports syntax/quick/full format for varying detail levels.C
Lookup Svelte 5 & SvelteKit definitions from TypeScript declarations. Covers all runes ($state, $derived, $props, $effect), features (snippets, onclick, component-events), and patterns. Supports syntax/quick/full format for varying detail levels.
| Name | Required | Description | Default |
|---|---|---|---|
| identifier | Yes | Svelte 5 identifier: $state, $derived, $props, $effect, snippets, onclick, component-events | |
| format | No | Output detail level: "syntax" (signature only), "quick" (with example), "full" (complete docs) | full |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the tool's function and output formats but does not cover critical aspects such as whether this is a read-only operation, potential rate limits, error handling, or authentication requirements. For a lookup tool with zero annotation coverage, this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded, with two sentences that efficiently convey the tool's scope and functionality. Every sentence adds value without redundancy, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is partially complete. It covers the purpose and parameters but lacks behavioral details and usage guidelines. Without an output schema, it does not explain return values, which is a gap, but the description compensates somewhat by mentioning output formats.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with clear descriptions for both parameters. The description adds minimal value beyond the schema by mentioning the coverage of runes and features, which relates to the 'identifier' parameter, but does not provide additional syntax or usage details. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It mentions what the tool covers and the output formats, but does not specify use cases, prerequisites, or exclusions. This leaves the agent without context for optimal tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has consistent naming since there are no other tools to compare against. The tool name 'svelte_definition' follows a clear noun-based pattern.
One tool is too few for a server that appears to cover Svelte 5 and SvelteKit definitions comprehensively. A single lookup tool feels thin and may not adequately support varied agent workflows, suggesting an incomplete or overly narrow implementation.
The server's domain is Svelte documentation, but with only a definition lookup tool, there are significant gaps. Missing are tools for examples, tutorials, API references beyond definitions, or interactive features, which limits agent effectiveness in handling broader documentation tasks.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
The official Svelte MCP server providing docs and autofixing tools for Svelte development
MCP server for langchain documentation, generated by doc2mcp.
MCP server for querying Forkast documentation
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context22265MIT
- AlicenseNot gradedqualityDmaintenanceGeneric MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.MIT
- AlicenseAqualityDmaintenanceMCP server for semantic search across llms.txt documentation sources, with hybrid two-stage retrieval and automatic background refresh.5MIT
- AlicenseAqualityBmaintenanceA local MCP server that fetches official library documentation (llms.txt-first), caches it to disk, and serves relevant sections to coding agents offline with deterministic retrieval.34MIT
Appeared in Searches
- A server for handling vector memory operations
- MCP integration with LangChain documentation
- A server or tool using RAG for documentation scraping, storage, and retrieval with SSE support
- Retrieve the latest documentation of libraries in word embeddings form for LLMs
- Official Documentation for Tailwind CSS
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/spences10/mcp-svelte-docs'
If you have feedback or need assistance with the MCP directory API, please join our Discord server