模型上下文协议 (MCP) 服务器提供 Svelte 5 的全面参考指南，帮助 LLM 在用户使用 Svelte 时提供准确的指导。它不仅包含从 Svelte 4 到 Svelte 5 的迁移模式，还可作为 Svelte 5 功能、常见错误和最佳实践的详细参考。
Claude Desktop（通过 WSL）
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "wsl.exe",
"args": ["bash", "-c", "npx -y mcp-svelte-docs"]
}
}
}风帆冲浪（通过 WSL）
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "wsl.exe",
"args": ["bash", "-c", "npx -y mcp-svelte-docs"]
}
}
}Windows（不含 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"]
}
}
}Related MCP server: mcp-docs
欢迎贡献代码！欢迎提交 Pull 请求。
MIT 许可证 - 有关详细信息，请参阅LICENSE文件。
构建于：
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 |
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.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0svelte_definitionsvelte5_component_eventssvelte5_derivedsvelte5_effectsvelte5_eventssvelte5_global_statesvelte5_migrationsvelte5_mistakessvelte5_overviewsvelte5_propssvelte5_runes_overviewsvelte5_snippetssvelte5_statesvelte5_component_eventssvelte5_derivedsvelte5_effectsvelte5_eventssvelte5_global_statesvelte5_migrationsvelte5_mistakessvelte5_overviewsvelte5_propssvelte5_runes_overviewsvelte5_snippetssvelte5_stateScored across 1 tool
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.
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.
