Claude Code Policy: Write Managed Settings Fast
Read More
Enterprise Connectors
Svelte logo. Svelte MCP server connector.

Svelte MCP Server

The official Svelte MCP server providing docs and autofixing tools for Svelte development

ToolsTools
4
Last updatedLast Updated
Jun 14, 2026
CategoryCategory
All
Install with Willow
Claude
Install
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the Svelte MCP Server?

The Svelte MCP server gives AI agents structured, permission-aware access to Svelte through the Model Context Protocol. With 4 pre-built actions, agents can read, create, and update Svelte data on behalf of authorized users.

Willow ships the Svelte MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Svelte is being used by every AI agent in your stack.

Tools

Tool

get-documentation

Retrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "cli/overview"). Can accept a single section name or an array of sections. Before running this, make sure to analyze the users query, as well as the output from list-sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to fetch all relevant runes, and so on. Before calling this tool, try to implement Svelte components using your own knowledge and the `svelte-autofixer` tool, since calling this tool is token intensive.
Tool

list-sections

Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get_documentation to fetch ALL relevant sections at once.
Tool

playground-link

Generates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code in the playground before calling this tool. NEVER use this tool if you have written the component to a file in the user project. The playground accept multiple files so if are importing from other files just include them all at the root level.
Tool

svelte-autofixer

Given a svelte component or module returns a list of suggestions to fix any issues it has. This tool MUST be used whenever the user is asking to write svelte code before sending the code back to the user
Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your Svelte MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-svelte": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/svelte"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-svelte": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/svelte"
    }
  }
}

Claude Code

CLI
claude mcp add willow-svelte --transport http https://<org>.mcp-s.com/mcp/mcp/svelte

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/svelte",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Svelte

Willow adds the layer Svelte and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Svelte MCP Server FAQ

What is the Svelte MCP server?

The Svelte MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Svelte data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Svelte MCP server different from the official one?

The official Svelte MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Svelte MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Svelte MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Svelte, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Svelte actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Svelte MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Svelte MCP locally, you'll see it.

What does the Svelte MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Svelte MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Willow vs ArchestraWillow vs CloudflareWillow vs MetaMCPWillow vs ObotWillow vs MintMCPWillow vs Runlayer

Related MCP Servers

100Hires logo. 100Hires MCP server connector.

100Hires

verified

100Hires MCP server. 131 governed tools.

4bots logo. 4bots MCP server connector.

4bots

verified

4bots MCP server. 9 governed tools.

Aeo logo. Aeo MCP server connector.

Aeo

verified

Aeo MCP server. 2 governed tools.

Affinity logo. Affinity MCP server connector.

Affinity

verified

Affinity MCP server. 10 governed tools.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.

Get Started
Get started
Book a Demo
Svelte MCP Server | Willow