The Model Context Protocol (MCP) server for Svelte 5 and SvelteKit provides comprehensive documentation to help AI assistants give accurate guidance when users are working with Svelte. It includes detailed information about Svelte 5 core features, modern async patterns, SvelteKit remote functions, migration paths, common mistakes, and advanced patterns.
To use this MCP server, you need to configure it with your AI assistant tool. Here are setup instructions for different environments:
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "wsl.exe",
"args": ["bash", "-c", "npx -y mcp-svelte-docs"]
}
}
}
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "npx",
"args": ["-y", "mcp-svelte-docs"]
}
}
}
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "npx",
"args": ["-y", "mcp-svelte-docs"]
}
}
}
The MCP server provides 16 specialized tools organized into different categories:
svelte5_state
- Documentation for $state
rune (reactive state)svelte5_derived
- Documentation for $derived
rune (computed values)svelte5_props
- Documentation for $props
rune (component properties)svelte5_effect
- Documentation for $effect
rune (side effects)svelte5_snippets
- Documentation for snippets (replacement for slots)svelte5_events
- Event handling patterns in Svelte 5svelte5_component_events
- Component event patterns and best practicessvelte5_global_state
- Global state management patternssvelte5_await_expressions
- Await expressions for async operations (experimental)sveltekit_remote_functions
- Remote functions for type-safe client-server communication (experimental)svelte5_migration
- Migration patterns from Svelte 4 to Svelte 5svelte5_mistakes
- Common mistakes and how to avoid themsvelte5_overview
- General overview of Svelte 5 featuressvelte5_runes_overview
- Comprehensive overview of all runesAll tools support an optional includeExamples
parameter:
{
"includeExamples": true
}
true
(default), the tool will include code examples and demonstrationsfalse
, the tool will return documentation without code examples for a more concise referenceThe MCP server provides documentation on:
await
expressions directly in components, $derived
, and markup<svelte:boundary>
The server includes information about:
You'll find:
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "mcp-svelte-docs" '{"command":"npx","args":["-y","mcp-svelte-docs"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "npx",
"args": [
"-y",
"mcp-svelte-docs"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"mcp-svelte-docs": {
"command": "npx",
"args": [
"-y",
"mcp-svelte-docs"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect