feat: wip github webhook

.changeset/README.md

@@ -1,8 +0,0 @@
-# Changesets
-
-Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
-with multi-package repos, or single-package repos to help you version and publish your code. You can
-find the full documentation for it [in our repository](https://github.com/changesets/changesets)
-
-We have a quick list of common questions to get you started engaging with this project in
-[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/config.json

@@ -1,11 +0,0 @@
-{
-	"$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
-	"changelog": ["@svitejs/changesets-changelog-github-compact", { "repo": "sveltejs/mcp" }],
-	"commit": false,
-	"fixed": [],
-	"linked": [],
-	"access": "public",
-	"baseBranch": "main",
-	"updateInternalDependencies": "patch",
-	"ignore": []
-}

.github/workflows/check.yml

@@ -18,7 +18,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 10.17.1
+          version: 10
 
       - name: Setup Node.js
         uses: actions/setup-node@v4

.github/workflows/lint.yml

@@ -18,7 +18,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 10.17.1
+          version: 10
 
       - name: Setup Node.js
         uses: actions/setup-node@v4

.github/workflows/release.yml

@@ -1,58 +0,0 @@
-name: Release
-
-on:
-  push:
-    branches:
-      - main
-permissions: {}
-
-jobs:
-  release:
-    permissions:
-      contents: write # to create release (changesets/action)
-      id-token: write # OpenID Connect token needed for provenance
-      pull-requests: write # to create pull request (changesets/action)
-    # prevents this action from running on forks
-    if: github.repository == 'sveltejs/mcp'
-    name: Release
-    runs-on: ${{ matrix.os }}
-    strategy:
-      matrix:
-        # pseudo-matrix for convenience, NEVER use more than a single combination
-        node: [24]
-        os: [ubuntu-latest]
-    steps:
-      - name: checkout
-        uses: actions/checkout@v5
-        with:
-          # This makes Actions fetch all Git history so that Changesets can generate changelogs with the correct commits
-          fetch-depth: 0
-      - uses: actions/setup-node@v5
-        with:
-          node-version: ${{ matrix.node }}
-          package-manager-cache: false # pnpm is not installed yet
-      - name: install pnpm
-        shell: bash
-        run: |
-          PNPM_VER=$(jq -r '.packageManager | if .[0:5] == "pnpm@" then .[5:] else "packageManager in package.json does not start with pnpm@\n" | halt_error(1)  end' package.json)
-          echo installing pnpm version $PNPM_VER
-          npm i -g pnpm@$PNPM_VER
-      - uses: actions/setup-node@v5
-        with:
-          node-version: ${{ matrix.node }}
-          package-manager-cache: true # caches pnpm via packageManager field in package.json
-      - name: install
-        run: pnpm install --frozen-lockfile --prefer-offline --ignore-scripts
-      - name: build
-        run: pnpm run --filter ./packages/mcp-stdio/ build
-
-      - name: Create Release Pull Request or Publish to npm
-        id: changesets
-        # pinned for security, always review third party action code before updating
-        uses: changesets/action@e0145edc7d9d8679003495b11f87bd8ef63c0cba # v1.5.3
-        with:
-          # This expects you to have a script called release which does a build for your packages and calls changeset publish
-          publish: pnpm release
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NPM_CONFIG_PROVENANCE: true

.github/workflows/test.yml

@@ -18,7 +18,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 10.17.1
+          version: 10
 
       - name: Setup Node.js
         uses: actions/setup-node@v4

.mcp.json

@@ -1,9 +1,8 @@
 {
 	"mcpServers": {
-		"svelte": {
-			"type": "stdio",
-			"command": "node",
-			"args": ["packages/mcp-stdio/dist/index.js"]
+		"svelte-llm": {
+			"type": "http",
+			"url": "https://svelte-llm.stanislav.garden/mcp/mcp"
 		}
 	}
 }

.prettierignore

@@ -8,7 +8,4 @@ bun.lockb
 # Miscellaneous
 /static/
 /drizzle/
-/**/.svelte-kit/*
-
-# Claude Code
-.claude/
+/**/.svelte-kit/*

.vscode/mcp.json

@@ -3,7 +3,7 @@
 		"Svelte MCP": {
 			"type": "stdio",
 			"command": "node",
-			"args": ["packages/mcp-stdio/dist/index.js"]
+			"args": ["dist/lib/stdio.js"]
 		}
 	},
 	"inputs": []

CLAUDE.md

@@ -90,12 +90,12 @@ When connected to the svelte-llm MCP server, you have access to comprehensive Sv
 
 ## Available MCP Tools:
 
-### 1. list-sections
+### 1. list_sections
 
 Use this FIRST to discover all available documentation sections. Returns a structured list with titles 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
+### 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 and then use the get_documentation tool to fetch ALL documentation sections that are relevant for the users task.
+After calling the list_sections tool, you MUST analyze the returned documentation sections and then use the get_documentation tool to fetch ALL documentation sections that are relevant for the users task.

README.md

@@ -6,7 +6,7 @@ Repo for the official Svelte MCP server.
 
 ```
 pnpm i
-cp apps/mcp-remote/.env.example apps/mcp-remote/.env
+cp .env.example .env
 pnpm dev
 ```
 

apps/mcp-remote/.env.example

@@ -1,3 +1,4 @@
 DATABASE_URL=file:test.db
 DATABASE_TOKEN=needs_to_be_set_but_it_can_be_anything
-VOYAGE_API_KEY=your_actual_api_key_here
+VOYAGE_API_KEY=your_actual_api_key_here
+GITHUB_WEBHOOK_SECRET=some_secret

apps/mcp-remote/package.json

@@ -65,6 +65,7 @@
 		"@sveltejs/mcp-schema": "workspace:^",
 		"@sveltejs/mcp-server": "workspace:^",
 		"@tmcp/transport-http": "^0.6.3",
-		"tmcp": "^1.14.0"
+		"tmcp": "^1.14.0",
+		"valibot": "^1.1.0"
 	}
 }

apps/mcp-remote/src/hooks.server.ts

@@ -1,19 +1,7 @@
 import { http_transport } from '$lib/mcp/index.js';
 import { db } from '$lib/server/db/index.js';
-import { redirect } from '@sveltejs/kit';
 
 export async function handle({ event, resolve }) {
-	if (event.request.method === 'GET') {
-		const accept = event.request.headers.get('accept');
-		if (accept) {
-			const accepts = accept.split(',');
-			if (!accepts.includes('text/event-stream')) {
-				// the request it's a browser request, not an MCP client request
-				// it means someone probably opened it from the docs...we should redirect to the docs
-				redirect(302, 'https://svelte.dev/docs/mcp/overview');
-			}
-		}
-	}
 	const mcp_response = await http_transport.respond(event.request, {
 		db,
 	});

apps/mcp-remote/src/lib/schemas/index.ts

@@ -0,0 +1,32 @@
+import * as v from 'valibot';
+
+// not the full schema but it contains the information we need
+export const github_webhook_schema = v.object({
+	action: v.union([v.literal('closed')]),
+	pull_request: v.object({
+		patch_url: v.string(),
+		merged: v.boolean(),
+		user: v.object({
+			login: v.string(),
+		}),
+	}),
+});
+
+export const github_content_schema = v.object({
+	name: v.string(),
+	path: v.string(),
+	sha: v.string(),
+	size: v.number(),
+	url: v.string(),
+	html_url: v.string(),
+	git_url: v.string(),
+	download_url: v.nullable(v.string()),
+	type: v.literal('file'),
+	content: v.string(),
+	encoding: v.literal('base64'),
+	_links: v.object({
+		self: v.string(),
+		git: v.string(),
+		html: v.string(),
+	}),
+});

apps/mcp-remote/src/routes/webhooks/docs/+server.ts

@@ -0,0 +1,54 @@
+import { github_content_schema, github_webhook_schema } from '$lib/schemas/index.js';
+import * as v from 'valibot';
+
+export async function POST({ request, fetch }) {
+	const body = await request.json();
+	// TODO add secret validation
+	const validated_pull_request = v.safeParse(github_webhook_schema, body);
+	if (!validated_pull_request.success) {
+		return new Response('Invalid payload', { status: 400 });
+	}
+
+	const { pull_request } = validated_pull_request.output;
+
+	if (!pull_request.merged) {
+		return new Response(null, { status: 204 });
+	}
+
+	const patch = await fetch(pull_request.patch_url);
+	if (!patch.ok) {
+		return new Response('Failed to fetch patch', { status: 500 });
+	}
+
+	const patch_text = await patch.text();
+	const files = [
+		...patch_text.matchAll(
+			/^diff --git\sa\/(?<file>.+?)\sb\/\1\n(?:(?<action>deleted|new)\sfile mode)?/gm,
+		),
+	].map((res) => ({ file: res.groups!.file, action: res.groups?.action ?? 'modified' }));
+
+	for (const file of files) {
+		if (file.action === 'deleted') {
+			// delete path from db
+			continue;
+		}
+		const new_file_content = await fetch(
+			`https://api.github.com/repos/sveltejs/svelte.dev/contents/${file.file}`,
+		);
+		if (!new_file_content.ok) {
+			// push file in queue and try again later?
+			continue;
+		}
+		const new_file_json = await new_file_content.json();
+		const validated_content = v.safeParse(github_content_schema, new_file_json);
+		if (!validated_content.success) {
+			// push file in queue and try again later?
+			continue;
+		}
+		const content = Buffer.from(validated_content.output.content, 'base64').toString('utf-8');
+		// save content and distilled content in the db
+		console.log({ content, file: file.file });
+	}
+
+	return new Response(null, { status: 204 });
+}

documentation/docs/10-introduction/10-overview.md

@@ -1,44 +0,0 @@
----
-title: Overview
----
-
-The Svelte MCP ([Model Context Protocol](https://modelcontextprotocol.io/docs/getting-started/intro)) server can help your LLM or agent of choice write better Svelte code. It works by providing documentation relevant to the task at hand, and statically analysing generated code so that it can suggest fixes and best practices.
-
-## Setup
-
-The setup varies based on the version of the MCP you prefer — remote or local — and your chosen MCP client (e.g. Claude Code, Codex CLI or GitHub Copilot):
-
-- [local setup](local-setup) using `@sveltejs/mcp`
-- [remote setup](remote-setup) using [mcp.svelte.dev/mcp](https://mcp.svelte.dev/mcp)
-
-## Usage
-
-To get the most out of the MCP server we recommend including the following prompt in your `AGENTS.md` (or `CLAUDE.md`, if using Claude Code). This will tell the LLM which tools are available and when it's appropriate to use them.
-
-```md
-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 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.
-```
-
-If your MCP client supports it, we also recommend using the [svelte-task](prompts#svelte-task) prompt to instruct the LLM on the best way to use the MCP server.

documentation/docs/10-introduction/index.md

@@ -1,3 +0,0 @@
----
-title: Introduction
----

documentation/docs/20-setup/20-local-setup.md

@@ -1,113 +0,0 @@
----
-title: Local setup
----
-
-The local (or stdio) version of the MCP server is available via the [`@sveltejs/mcp`](https://www.npmjs.com/package/@sveltejs/mcp) npm package. You can either install it globally and then reference it in your configuration or run it with `npx`:
-
-```bash
-npx -y @sveltejs/mcp
-```
-
-Here's how to set it up in some common MCP clients:
-
-## Claude Code
-
-To include the local MCP version in Claude Code, simply run the following command:
-
-```bash
-claude mcp add -t stdio -s [scope] svelte npx -y @sveltejs/mcp
-```
-
-The `[scope]` must be `user`, `project` or `local`.
-
-## Claude Desktop
-
-In the Settings > Developer section, click on Edit Config. It will open the folder with a `claude_desktop_config.json` file in it. Edit the file to include the following configuration:
-
-```json
-{
-	"mcpServers": {
-		"svelte": {
-			"command": "npx",
-			"args": ["-y", "@sveltejs/mcp"]
-		}
-	}
-}
-```
-
-## Codex CLI
-
-Add the following to your `config.toml` (which defaults to `~/.codex/config.toml`, but refer to [the configuration documentation](https://github.com/openai/codex/blob/main/docs/config.md) for more advanced setups):
-
-```toml
-[mcp_servers.svelte]
-command = "npx"
-args = ["-y", "@sveltejs/mcp"]
-```
-
-## Gemini CLI
-
-To include the local MCP version in Gemini CLI, simply run the following command:
-
-```bash
-gemini mcp add -t stdio -s [scope] svelte npx -y @sveltejs/mcp
-```
-
-The `[scope]` must be `user`, `project` or `local`.
-
-## OpenCode
-
-Run the command:
-
-```bash
-opencode mcp add
-```
-
-and follow the instructions, selecting 'Local' under the 'Select MCP server type' prompt:
-
-```bash
-opencode mcp add
-
-┌  Add MCP server
-│
-◇  Enter MCP server name
-│  svelte
-│
-◇  Select MCP server type
-│  Local
-│
-◆  Enter command to run
-│  npx -y @sveltejs/mcp
-```
-
-## VS Code
-
-- Open the command palette
-- Select "MCP: Add Server..."
-- Select "Command (stdio)"
-- Insert `npx -y @sveltejs/mcp` in the input and press `Enter`
-- When prompted for a name, insert `svelte`
-- Select if you want to add it as a `Global` or `Workspace` MCP server
-
-## Cursor
-
-- Open the command palette
-- Select "View: Open MCP Settings"
-- Click on "Add custom MCP"
-
-It will open a file with your MCP servers where you can add the following configuration:
-
-```json
-{
-	"mcpServers": {
-		"svelte": {
-			"command": "npx",
-			"args": ["-y", "@sveltejs/mcp"]
-		}
-	}
-}
-```
-
-## Other clients
-
-If we didn't include the MCP client you are using, refer to their documentation for `stdio` servers and use `npx` as the command and `-y @sveltejs/mcp` as the arguments.

documentation/docs/20-setup/30-remote-setup.md

@@ -1,101 +0,0 @@
----
-title: Remote setup
----
-
-The remote version of the MCP server is available on `https://mcp.svelte.dev/mcp`.
-
-Here's how to set it up in some common MCP clients:
-
-## Claude Code
-
-To include the remote MCP version in Claude Code, simply run the following command:
-
-```bash
-claude mcp add -t http -s [scope] svelte https://mcp.svelte.dev/mcp
-```
-
-You can choose your preferred `scope` (it must be `user`, `project` or `local`) and `name`.
-
-## Claude Desktop
-
-- Open Settings > Connectors
-- Click on Add Custom Connector
-- When prompted for a name, enter `svelte`
-- Under the Remote MCP server URL input, use `https://mcp.svelte.dev/mcp`
-- Click Add
-
-## Codex CLI
-
-Add the following to your `config.toml` (which defaults to `~/.codex/config.toml`, but refer to [the configuration documentation](https://github.com/openai/codex/blob/main/docs/config.md) for more advanced setups):
-
-```toml
-experimental_use_rmcp_client = true
-[mcp_servers.svelte]
-url = "https://mcp.svelte.dev/mcp"
-```
-
-## Gemini CLI
-
-To use the remote MCP server with Gemini CLI, simply run the following command:
-
-```bash
-gemini mcp add -t http -s [scope] svelte https://mcp.svelte.dev/mcp
-```
-
-The `[scope]` must be `user`, `project` or `local`.
-
-## OpenCode
-
-Run the command:
-
-```bash
-opencode mcp add
-```
-
-and follow the instructions, selecting 'Remote' under the 'Select MCP server type' prompt:
-
-```bash
-opencode mcp add
-
-┌  Add MCP server
-│
-◇  Enter MCP server name
-│  svelte
-│
-◇  Select MCP server type
-│  Remote
-│
-◇  Enter MCP server URL
-│  https://mcp.svelte.dev/mcp
-```
-
-## VS Code
-
-- Open the command palette
-- Select "MCP: Add Server..."
-- Select "HTTP (HTTP or Server-Sent-Events)"
-- Insert `https://mcp.svelte.dev/mcp` in the input and press `Enter`
-- Insert your preferred name
-- Select if you want to add it as a `Global` or `Workspace` MCP server
-
-## Cursor
-
-- Open the command palette
-- Select "View: Open MCP Settings"
-- Click on "Add custom MCP"
-
-It will open a file with your MCP servers where you can add the following configuration:
-
-```json
-{
-	"mcpServers": {
-		"svelte": {
-			"url": "https://mcp.svelte.dev/mcp"
-		}
-	}
-}
-```
-
-## Other clients
-
-If we didn't include the MCP client you are using, refer to their documentation for `remote` servers and use `https://mcp.svelte.dev/mcp` as the URL.

documentation/docs/20-setup/index.md

@@ -1,3 +0,0 @@
----
-title: Setup
----

documentation/docs/30-capabilities/10-tools.md

@@ -1,21 +0,0 @@
----
-title: Tools
----
-
-The following tools are provided by the MCP server to the model, which can decide to call one or more of them during a session:
-
-## list-sections
-
-Provides a list of all the available documentation sections.
-
-## get-documentation
-
-Allows the model to get the full (and up-to-date) documentation for the requested sections directly from [svelte.dev/docs](/docs).
-
-## svelte-autofixer
-
-Uses static analysis to provide suggestions for the generated code. It should be invoked in a loop by the model until all issues and suggestions are resolved.
-
-## playground-link
-
-Generates an ephemeral playground link with the generated code. It's useful when the generated code is not written to a file in your project and you want to quickly test the generated solution. The code is not stored anywhere except the URL itself (which will often, as a consequence, be quite large).

documentation/docs/30-capabilities/20-resources.md

@@ -1,9 +0,0 @@
----
-title: Resources
----
-
-This is the list of available resources provided by the MCP server. Resources are included by the user (not by the LLM) and are useful if you want to include specific knowledge in your session. For example, if you know that the component will need to use transitions you can include the transition documentation directly without asking the LLM to do it for you.
-
-## doc-section
-
-This dynamic resource allows you to add every section of the Svelte documentation as a resource. The URI looks like this `svelte://slug-of-the-docs.md` and the returned resource will contain the `llms.txt` version of the specific page you selected.

documentation/docs/30-capabilities/30-prompts.md

@@ -1,26 +0,0 @@
----
-title: Prompts
----
-
-This is the list of available prompts provided by the MCP server. Prompts are selected by the user and are sent as a user message. They can be useful to write repetitive instructions for the LLM on how to properly use the MCP server.
-
-## svelte-task
-
-This prompt should be used whenever you are asking the model to work on some Svelte-related task. It will instruct the LLM on which documentation sections are available, which tool to invoke, when to invoke it, and how to interpret the result. It will ask you for the description of the task and the returned value will look like this:
-
-```
-You are a Svelte expert tasked to build components and utilities for Svelte developers. If you need documentation for anything related to Svelte you can invoke the tool \`get-documentation\` with one of the following paths:
-<available-docs-paths>
-[all available docs]
-</available-docs-paths>
-
-Every time you write a Svelte component or a Svelte module you MUST invoke the \`svelte-autofixer\` tool providing the code. The tool will return a list of issues or suggestions. If there are any issues or suggestions you MUST fix them and call the tool again with the updated code. You MUST keep doing this until the tool returns no issues or suggestions. Only then you can return the code to the user.
-
-This is the task you will work on:
-
-<task>
-[your task here]
-</task>
-
-If you are not writing the code into a file, once you have the final version of the code ask the user if they want to generate a playground link to quickly check the code in it and if they answer yes call the \`playground-link\` tool and return the url to the user nicely formatted. The playground link MUST be generated only once you have the final version of the code and you are ready to share it, it MUST include an entry point file called \`App.svelte\` where the main component should live. If you have multiple files to include in the playground link you can include them all at the root.
-```

documentation/docs/30-capabilities/index.md

@@ -1,3 +0,0 @@
----
-title: Capabilities
----

documentation/docs/index.md

@@ -1,3 +0,0 @@
----
-title: MCP
----

eslint.config.js

@@ -12,9 +12,6 @@ const gitignore_path = fileURLToPath(new URL('./.gitignore', import.meta.url));
 
 export default /** @type {import("eslint").Linter.Config} */ ([
 	includeIgnoreFile(gitignore_path),
-	{
-		ignores: ['.claude/**/*'],
-	},
 	js.configs.recommended,
 	...ts.configs.recommended,
 	...svelte.configs.recommended,

package.json

@@ -3,20 +3,16 @@
 	"version": "0.0.1",
 	"description": "The official Svelte MCP server implementation",
 	"type": "module",
-	"packageManager": "pnpm@10.17.1",
 	"scripts": {
 		"build": "pnpm -r run build",
-		"dev": "pnpm --filter @sveltejs/mcp-remote run dev",
 		"check": "pnpm -r run check",
-		"check:publint": "pnpm -r run check:publint",
 		"format": "prettier --write .",
 		"lint": "prettier --check . && eslint .",
 		"lint:fix": "prettier --write . && eslint . --fix",
 		"test:unit": "vitest",
 		"test": "npm run test:unit -- --run",
 		"test:watch": "npm run test:unit -- --watch",
-		"inspect": "pnpm mcp-inspector",
-		"release": "pnpm --filter @sveltejs/mcp run build && changeset publish"
+		"inspect": "pnpm mcp-inspector"
 	},
 	"keywords": [
 		"svelte",
@@ -26,11 +22,9 @@
 	],
 	"private": true,
 	"devDependencies": {
-		"@changesets/cli": "^2.29.7",
 		"@eslint/compat": "^1.3.2",
 		"@eslint/js": "^9.36.0",
 		"@modelcontextprotocol/inspector": "^0.16.7",
-		"@svitejs/changesets-changelog-github-compact": "^1.2.0",
 		"eslint": "^9.36.0",
 		"eslint-config-prettier": "^10.0.1",
 		"eslint-plugin-import": "^2.32.0",
@@ -38,7 +32,6 @@
 		"globals": "^16.0.0",
 		"prettier": "^3.4.2",
 		"prettier-plugin-svelte": "^3.3.3",
-		"publint": "^0.3.13",
 		"typescript": "^5.0.0",
 		"typescript-eslint": "^8.44.1",
 		"vitest": "^3.2.3"

packages/mcp-schema/package.json

@@ -12,6 +12,7 @@
 	"keywords": [],
 	"author": "",
 	"license": "ISC",
+	"packageManager": "pnpm@10.15.1",
 	"type": "module",
 	"dependencies": {
 		"drizzle-orm": "^0.40.1"

packages/mcp-server/package.json

@@ -7,6 +7,7 @@
 	"keywords": [],
 	"author": "",
 	"license": "ISC",
+	"packageManager": "pnpm@10.15.1",
 	"type": "module",
 	"scripts": {
 		"test": "vitest"

packages/mcp-server/src/mcp/handlers/prompts/svelte-task.ts

@@ -1,6 +1,5 @@
 import type { SvelteMcp } from '../../index.js';
 import * as v from 'valibot';
-import { get_sections } from '../../utils.js';
 
 export function setup_svelte_task(server: SvelteMcp) {
 	server.prompt(
@@ -14,7 +13,8 @@ export function setup_svelte_task(server: SvelteMcp) {
 			}),
 		},
 		async ({ task }) => {
-			const available_docs: string[] = (await get_sections()).map((s) => s.title);
+			// TODO: implement logic to fetch the available docs paths to return in the prompt
+			const available_docs: string[] = [];
 
 			return {
 				messages: [
@@ -22,7 +22,7 @@ export function setup_svelte_task(server: SvelteMcp) {
 						role: 'user',
 						content: {
 							type: 'text',
-							text: `You are a Svelte expert tasked to build components and utilities for Svelte developers. If you need documentation for anything related to Svelte you can invoke the tool \`get-documentation\` with one of the following paths:
+							text: `You are a Svelte expert tasked to build components and utilities for Svelte developers. If you need documentation for anything related to Svelte you can invoke the tool \`get_documentation\` with one of the following paths:
 <available-docs-paths>						
 ${JSON.stringify(available_docs, null, 2)}
 </available-docs-paths>

packages/mcp-server/src/mcp/handlers/resources/doc-section.ts

@@ -1,64 +0,0 @@
-import type { SvelteMcp } from '../../index.js';
-import { get_sections, fetch_with_timeout } from '../../utils.js';
-
-export async function list_sections(server: SvelteMcp) {
-	const sections = await get_sections();
-
-	server.template(
-		{
-			name: 'Svelte Doc Section',
-			description: 'A single documentation section',
-			list() {
-				return sections.map((section) => {
-					const section_name = section.slug;
-					const resource_name = section_name;
-					const resource_uri = `svelte://${section_name}.md`;
-					return {
-						name: resource_name,
-						description: section.use_cases,
-						uri: resource_uri,
-						title: section.title,
-					};
-				});
-			},
-			complete: {
-				slug: (query) => {
-					const values = sections
-						.reduce<string[]>((acc, section) => {
-							const section_name = section.slug;
-							const resource_name = section_name;
-							if (section_name.includes(query.toLowerCase())) {
-								acc.push(resource_name);
-							}
-							return acc;
-						}, [])
-						// there's a hard limit of 100 for completions
-						.slice(0, 100);
-					return {
-						completion: {
-							values,
-						},
-					};
-				},
-			},
-			uri: 'svelte://{/slug*}.md',
-		},
-		async (uri, { slug }) => {
-			const section = sections.find((section) => {
-				return slug === section.slug;
-			});
-			if (!section) throw new Error(`Section not found: ${slug}`);
-			const response = await fetch_with_timeout(section.url);
-			const content = await response.text();
-			return {
-				contents: [
-					{
-						uri,
-						type: 'text',
-						text: content,
-					},
-				],
-			};
-		},
-	);
-}

packages/mcp-server/src/mcp/handlers/resources/index.ts

@@ -1 +1 @@
-export * from './doc-section.js';
+export * from './list-sections.js';

packages/mcp-server/src/mcp/handlers/resources/list-sections.ts

@@ -0,0 +1,25 @@
+import type { SvelteMcp } from '../../index.js';
+
+export function list_sections(server: SvelteMcp) {
+	server.resource(
+		{
+			name: 'list-sections',
+			enabled: () => false,
+			description:
+				'The list of all the available Svelte 5 and SvelteKit documentation sections in a structured format.',
+			uri: 'svelte://list-sections',
+			title: 'Svelte Documentation Section',
+		},
+		async (uri) => {
+			return {
+				contents: [
+					{
+						uri,
+						type: 'text',
+						text: 'resource list-sections called',
+					},
+				],
+			};
+		},
+	);
+}

packages/mcp-server/src/mcp/handlers/tools/get-documentation.ts

@@ -1,7 +1,5 @@
 import type { SvelteMcp } from '../../index.js';
 import * as v from 'valibot';
-import { get_sections, fetch_with_timeout } from '../../utils.js';
-import { SECTIONS_LIST_INTRO, SECTIONS_LIST_OUTRO } from './prompts.js';
 
 export function get_documentation(server: SvelteMcp) {
 	server.tool(
@@ -9,7 +7,7 @@ export function get_documentation(server: SvelteMcp) {
 			name: 'get-documentation',
 			enabled: () => false,
 			description:
-				'Retrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "docs/svelte/state.md"). 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.',
+				'Retrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "docs/svelte/state.md"). 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.',
 			schema: v.object({
 				section: v.pipe(
 					v.union([v.string(), v.array(v.string())]),
@@ -19,7 +17,7 @@ export function get_documentation(server: SvelteMcp) {
 				),
 			}),
 		},
-		async ({ section }) => {
+		({ section }) => {
 			let sections: string[];
 
 			if (Array.isArray(section)) {
@@ -45,73 +43,13 @@ export function get_documentation(server: SvelteMcp) {
 				sections = [];
 			}
 
-			const available_sections = await get_sections();
-
-			const settled_results = await Promise.allSettled(
-				sections.map(async (requested_section) => {
-					const matched_section = available_sections.find(
-						(s) =>
-							s.title.toLowerCase() === requested_section.toLowerCase() ||
-							s.url === requested_section,
-					);
-
-					if (matched_section) {
-						try {
-							const response = await fetch_with_timeout(matched_section.url);
-							if (response.ok) {
-								const content = await response.text();
-								return { success: true, content: `## ${matched_section.title}\n\n${content}` };
-							} else {
-								return {
-									success: false,
-									content: `## ${matched_section.title}\n\nError: Could not fetch documentation (HTTP ${response.status})`,
-								};
-							}
-						} catch (error) {
-							return {
-								success: false,
-								content: `## ${matched_section.title}\n\nError: Failed to fetch documentation - ${error}`,
-							};
-						}
-					} else {
-						return {
-							success: false,
-							content: `## ${requested_section}\n\nError: Section not found.`,
-						};
-					}
-				}),
-			);
-
-			const results = settled_results.map((result) => {
-				if (result.status === 'fulfilled') {
-					return result.value;
-				} else {
-					return {
-						success: false,
-						content: `Error: Couldn't fetch - ${result.reason}`,
-					};
-				}
-			});
-
-			const has_any_success = results.some((result) => result.success);
-			let final_text = results.map((r) => r.content).join('\n\n---\n\n');
-
-			if (!has_any_success) {
-				const formatted_sections = available_sections
-					.map(
-						(section) =>
-							`* title: ${section.title}, use_cases: ${section.use_cases}, path: ${section.url}`,
-					)
-					.join('\n');
-
-				final_text += `\n\n---\n\n${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`;
-			}
+			const sections_list = sections.length > 0 ? sections.join(', ') : 'no sections';
 
 			return {
 				content: [
 					{
 						type: 'text',
-						text: final_text,
+						text: `called for sections: ${sections_list}`,
 					},
 				],
 			};

packages/mcp-server/src/mcp/handlers/tools/list-sections.ts

@@ -1,6 +1,4 @@
 import type { SvelteMcp } from '../../index.js';
-import { get_sections } from '../../utils.js';
-import { SECTIONS_LIST_INTRO, SECTIONS_LIST_OUTRO } from './prompts.js';
 
 export function list_sections(server: SvelteMcp) {
 	server.tool(
@@ -8,22 +6,14 @@ export function list_sections(server: SvelteMcp) {
 			name: 'list-sections',
 			enabled: () => false,
 			description:
-				'Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Returns sections as a list of "* title: [section_title], use_cases: [use_cases], path: [file_path]" - you can use either the title or path when querying a specific section via the get_documentation tool. Always run list-sections first for any query related to Svelte development to discover available content.',
+				'Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Returns sections as a list of "* title: [section_title], path: [file_path]" - you can use either the title or path when querying a specific section via the get_documentation tool. Always run list_sections first for any query related to Svelte development to discover available content.',
 		},
-		async () => {
-			const sections = await get_sections();
-			const formatted_sections = sections
-				.map(
-					(section) =>
-						`* title: ${section.title}, use_cases: ${section.use_cases}, path: ${section.url}`,
-				)
-				.join('\n');
-
+		() => {
 			return {
 				content: [
 					{
 						type: 'text',
-						text: `${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`,
+						text: 'tool list_sections called',
 					},
 				],
 			};

packages/mcp-server/src/mcp/handlers/tools/prompts.ts

@@ -1,5 +0,0 @@
-export const SECTIONS_LIST_INTRO =
-	'List of available Svelte documentation sections and its inteneded uses:';
-
-export const SECTIONS_LIST_OUTRO =
-	'Use the title or path with the get-documentation tool to get more details about a specific section.';

packages/mcp-server/src/mcp/schemas/index.ts

@@ -1,12 +0,0 @@
-import * as v from 'valibot';
-
-export const documentation_sections_schema = v.record(
-	v.string(),
-	v.object({
-		metadata: v.object({
-			title: v.string(),
-			use_cases: v.optional(v.string()),
-		}),
-		slug: v.string(),
-	}),
-);

packages/mcp-server/src/mcp/utils.ts

@@ -1,31 +0,0 @@
-import * as v from 'valibot';
-import { documentation_sections_schema } from '../mcp/schemas/index.js';
-
-export async function fetch_with_timeout(
-	url: string,
-	timeout_ms: number = 10000,
-): Promise<Response> {
-	try {
-		const response = await fetch(url, { signal: AbortSignal.timeout(timeout_ms) });
-		return response;
-	} catch (error) {
-		if (error instanceof Error && error.name === 'AbortError') {
-			throw new Error(`Request timed out after ${timeout_ms}ms`);
-		}
-		throw error;
-	}
-}
-
-export async function get_sections() {
-	const sections = await fetch_with_timeout(
-		'https://svelte.dev/docs/experimental/sections.json',
-	).then((res) => res.json());
-	const validated_sections = v.safeParse(documentation_sections_schema, sections);
-	if (!validated_sections.success) return [];
-	return Object.entries(validated_sections.output).map(([, section]) => ({
-		title: section.metadata.title,
-		use_cases: section.metadata.use_cases ?? 'read document for use cases',
-		slug: section.slug,
-		url: `https://svelte.dev/${section.slug}/llms.txt`,
-	}));
-}

packages/mcp-stdio/CHANGELOG.md

@@ -1,7 +0,0 @@
-# @sveltejs/mcp
-
-## 0.0.2
-
-### Patch Changes
-
-- feat: latest version ([#25](https://github.com/sveltejs/mcp/pull/25))

packages/mcp-stdio/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@sveltejs/mcp",
-	"version": "0.0.2",
+	"version": "0.0.1",
 	"type": "module",
 	"license": "MIT",
 	"homepage": "https://github.com/sveltejs/mcp#readme",
@@ -22,11 +22,10 @@
 		"access": "public"
 	},
 	"scripts": {
-		"build": "tsdown && publint",
+		"build": "tsdown",
 		"dev": "tsdown --watch",
 		"test": "vitest",
-		"check": "tsc --noEmit",
-		"check:publint": "publint --strict"
+		"check": "tsc --noEmit"
 	},
 	"devDependencies": {
 		"@sveltejs/mcp-server": "workspace:^",