From 4f7ea2b3755fa9ca2c9c0699b5c8874d82d043bd Mon Sep 17 00:00:00 2001
From: Dominic Ferrando <dominicf2001@gmail.com>
Date: Sat, 25 Jul 2026 20:48:51 -0400
Subject: [PATCH] Add svelte mcp

---
 .mcp.json             |  8 ++++++++
 apps/portal/CLAUDE.md | 23 +++++++++++++++++++++++
 2 files changed, 31 insertions(+)
 create mode 100644 .mcp.json
 create mode 100644 apps/portal/CLAUDE.md

diff --git a/.mcp.json b/.mcp.json
new file mode 100644
index 0000000..8a58702
--- /dev/null
+++ b/.mcp.json
@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "svelte": {
+      "type": "http",
+      "url": "https://mcp.svelte.dev/mcp"
+    }
+  }
+}
\ No newline at end of file
diff --git a/apps/portal/CLAUDE.md b/apps/portal/CLAUDE.md
new file mode 100644
index 0000000..4711cd0
--- /dev/null
+++ b/apps/portal/CLAUDE.md
@@ -0,0 +1,23 @@
+You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
+
+## Available Svelte MCP Tools:
+
+### 1. list-sections
+
+Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths.
+When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections.
+
+### 2. get-documentation
+
+Retrieves full documentation content for specific sections. Accepts single or multiple sections.
+After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task.
+
+### 3. svelte-autofixer
+
+Analyzes Svelte code and returns issues and suggestions.
+You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned.
+
+### 4. playground-link
+
+Generates a Svelte Playground link with the provided code.
+After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.