Svelte Docs▌
by spences10
Svelte Docs lets you efficiently query and retrieve Svelte documentation, streamlining access to framework-specific reso
Integrates with Svelte documentation to enable efficient querying and retrieval of framework-specific content for development assistance.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Svelte developers learning the new v5 syntax
- / Teams migrating from Svelte 4 to 5
- / Getting quick reference for runes and TypeScript types
capabilities
- / Query Svelte 5 rune definitions ($state, $derived, $effect, etc.)
- / Get TypeScript signatures for Svelte components and features
- / Access migration guidance from Svelte 4 to 5
- / Retrieve event handling patterns and examples
- / Look up snippet syntax and modern Svelte features
- / Get documentation in different formats (syntax-only, quick, or full)
what it does
Provides authoritative Svelte 5 and SvelteKit documentation extracted from TypeScript declarations. Get precise syntax, parameters, and examples for runes, components, and migration patterns.
about
Svelte Docs is a community-built MCP server published by spences10 that provides AI assistants with tools and capabilities via the Model Context Protocol. Svelte Docs lets you efficiently query and retrieve Svelte documentation, streamlining access to framework-specific reso It is categorized under developer tools. This server exposes 1 tool that AI clients can invoke during conversations and coding sessions.
how to install
You can install Svelte Docs in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport. This server supports remote connections over HTTP, so no local installation is required.
license
MIT
Svelte Docs is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
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)
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 tools - 28+ 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,$bindable - Advanced 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:
FAQ
- What is the Svelte Docs MCP server?
- Svelte Docs is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Svelte Docs?
- This profile displays 34 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.8 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.8★★★★★34 reviews- ★★★★★Arya Ghosh· Dec 24, 2024
Svelte Docs has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Alexander Martin· Nov 15, 2024
Svelte Docs is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Nikhil Thompson· Nov 7, 2024
I recommend Svelte Docs for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Alexander Jackson· Oct 26, 2024
Strong directory entry: Svelte Docs surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★James Robinson· Oct 6, 2024
We wired Svelte Docs into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Alexander Sanchez· Sep 25, 2024
Svelte Docs has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Piyush G· Sep 21, 2024
Svelte Docs has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Nikhil Ndlovu· Sep 5, 2024
Svelte Docs reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Arjun Lopez· Aug 24, 2024
Useful MCP listing: Svelte Docs is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Tariq Garcia· Aug 16, 2024
According to our notes, Svelte Docs benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 34