feat: allow for local opencode config

.changeset/giant-pears-count.md

@@ -0,0 +1,5 @@
+---
+'@sveltejs/opencode': patch
+---
+
+feat: allow for local opencode config

.changeset/rich-wolves-double.md

@@ -1,5 +0,0 @@
----
-'@sveltejs/mcp': patch
----
-
-feat: display similar result & error at the end

.github/workflows/release.yml

@@ -17,7 +17,7 @@ jobs:
     name: Release
     runs-on: ${{ matrix.os }}
     outputs:
-      publishedPackages: ${{ steps.changesets.outputs.publishedPackages }}
+      published: ${{ steps.changesets.outputs.published }}
     strategy:
       matrix:
         # pseudo-matrix for convenience, NEVER use more than a single combination
@@ -64,7 +64,7 @@ jobs:
 
   publish-mcp:
     needs: release
-    if: contains(needs.release.outputs.publishedPackages, '"@sveltejs/mcp"')
+    if: needs.release.outputs.published == 'true'
     uses: ./.github/workflows/publish-mcp.yml
     secrets:
       MCP_KEY: ${{ secrets.MCP_KEY }}

.github/workflows/sync-agents-md.yml

@@ -1,71 +0,0 @@
-name: Sync Agents Documentation
-
-on:
-  push:
-    branches:
-      - main
-    paths:
-      - 'instructions/AGENTS.md'
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  sync-agents:
-    # prevents this action from running on forks
-    if: github.repository == 'sveltejs/mcp'
-    name: Sync AGENTS.md to OpenCode Package and Docs
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 0
-
-      - name: Setup Node.js
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
-        with:
-          node-version: 24
-          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
-
-      - name: Sync AGENTS.md
-        run: pnpm sync-agents-md
-
-      - name: Check for changes
-        id: git-check
-        run: |
-          git diff --exit-code packages/opencode/instructions/opencode-agents.md documentation/docs/10-introduction/.generated/agents.md || echo "changed=true" >> $GITHUB_OUTPUT
-
-      - name: Create Pull Request
-        if: steps.git-check.outputs.changed == 'true'
-        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          commit-message: 'chore: sync AGENTS.md to opencode package and documentation'
-          branch: chore/sync-agents-md
-          delete-branch: true
-          title: 'chore: sync AGENTS.md to opencode package and documentation'
-          body: |
-            ## Summary
-            Automatically synced AGENTS.md to the opencode package and documentation.
-
-            This PR was triggered by changes to `instructions/AGENTS.md`.
-
-            ## Changes
-            - Synced `packages/opencode/instructions/opencode-agents.md` with latest AGENTS.md
-            - Updated `documentation/docs/10-introduction/.generated/agents.md` with latest content
-
-            ## Generated by
-            GitHub Action: Sync Agents Documentation
-          labels: |
-            chore
-            documentation
-            automated

documentation/docs/10-introduction/.generated/agents.md

@@ -1,23 +0,0 @@
-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.

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

@@ -17,6 +17,30 @@ To get the most out of the MCP server we recommend including the following promp
 
 > [!NOTE] This is already setup for you when using `npx sv add mcp`
 
-@include .generated/agents.md
+```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/50-opencode-plugin/opencode-plugin.md

@@ -33,13 +33,10 @@ The default configuration for the Svelte OpenCode plugin looks like this...
 	},
 	"skills": {
 		"enabled": true
-	},
-	"instructions": {
-		"enabled": true
 	}
 }
 ```
 
 ...but if you prefer, you can enable only the subagent, only the MCP, only the skills, or configure the kind of MCP server you want to use (`local` or `remote`).
 
-You can place this file in `./.opencode/svelte.json` (in your project), in `~/.config/opencode/svelte.json` or, if you have an `OPENCODE_CONFIG_DIR` environment variable specified, at `$OPENCODE_CONFIG_DIR/svelte.json`.
+You can place this file in `~/.config/opencode/svelte.json` or, if you have an `OPENCODE_CONFIG_DIR` environment variable specified, at `$OPENCODE_CONFIG_DIR/svelte.json`.

documentation/docs/60-skills/.generated/skills.md

@@ -1,6 +1,6 @@
 ## `svelte-code-writer`
 
-CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
+CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
 
 <a href="https://github.com/sveltejs/mcp/releases?q=svelte-code-writer" target="_blank" rel="noopener noreferrer">Open Releases page</a>
 

instructions/AGENTS.md

@@ -1,23 +0,0 @@
-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.

package.json

@@ -25,8 +25,7 @@
 		"debug:generate-summaries": "pnpm --filter @sveltejs/mcp-server run debug:generate-summaries",
 		"release": "pnpm --filter @sveltejs/mcp run build && changeset publish",
 		"changeset:version": "changeset version && pnpm --filter @sveltejs/mcp run update:version && git add --all",
-		"sync-opencode-skills": "rm -rf packages/opencode/skills && cp -r plugins/svelte/skills packages/opencode/skills",
-		"sync-agents-md": "rm -f packages/opencode/instructions/opencode-agents.md && rm -f documentation/docs/10-introduction/.generated/agents.md && mkdir -p packages/opencode/instructions && mkdir -p documentation/docs/10-introduction/.generated && cp instructions/AGENTS.md packages/opencode/instructions/opencode-agents.md && cp instructions/AGENTS.md documentation/docs/10-introduction/.generated/agents.md"
+		"sync-opencode-skills": "rm -rf packages/opencode/skills && cp -r plugins/svelte/skills packages/opencode/skills"
 	},
 	"keywords": [
 		"svelte",

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

@@ -91,56 +91,16 @@ export async function get_documentation_handler({
 		}
 	});
 
-	const successes = results.filter((r) => r.success);
-	const failed_sections = sections.filter(
-		(s) =>
-			!available_sections.some(
-				(a) => a.title.toLowerCase() === s.toLowerCase() || a.slug === s || a.url === s,
-			),
-	);
+	const has_any_success = results.some((result) => result.success);
+	let final_text = results.map((r) => r.content).join('\n\n---\n\n');
 
-	if (successes.length > 0 && failed_sections.length === 0) {
-		return successes.map((r) => r.content).join('\n\n---\n\n');
-	}
-
-	const parts: string[] = [];
-
-	if (successes.length > 0) {
-		parts.push(successes.map((r) => r.content).join('\n\n---\n\n'));
-	}
-
-	const fuzzy_results = failed_sections.map((requested) => {
-		const lower = requested.toLowerCase();
-		const matches = available_sections.filter(
-			(a) =>
-				a.title.toLowerCase().includes(lower) ||
-				a.slug.includes(lower) ||
-				lower.includes(a.slug.split('/').pop() ?? '') ||
-				a.use_cases.toLowerCase().includes(lower),
-		);
-		return { requested, matches };
-	});
-
-	const has_fuzzy = fuzzy_results.some((r) => r.matches.length > 0);
-
-	// Full list only when no successes and no fuzzy matches
-	if (successes.length === 0 && !has_fuzzy) {
+	if (!has_any_success) {
 		const formatted_sections = await format_sections_list();
-		parts.push(`${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`);
+
+		final_text += `\n\n---\n\n${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`;
 	}
 
-	// Similar results then errors
-	for (const { requested, matches } of fuzzy_results) {
-		if (matches.length > 0) {
-			const match_list = matches.map((m) => `- title: ${m.title}, section: ${m.slug}`).join('\n');
-			parts.push(
-				`${matches.length} similar result${matches.length > 1 ? 's' : ''} for "${requested}":\n${match_list}`,
-			);
-		}
-		parts.push(`Section not found: "${requested}".`);
-	}
-
-	return parts.join('\n\n---\n\n');
+	return final_text;
 }
 
 export function get_documentation(server: SvelteMcp) {

packages/opencode/CHANGELOG.md

@@ -1,11 +1,5 @@
 # @sveltejs/opencode
 
-## 0.1.2
-
-### Patch Changes
-
-- feat: allow for local opencode config ([#156](https://github.com/sveltejs/mcp/pull/156))
-
 ## 0.1.1
 
 ### Patch Changes

packages/opencode/instructions/opencode-agents.md

@@ -1,6 +1,6 @@
 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:
+## Available MCP Tools:
 
 ### 1. list-sections
 

packages/opencode/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@sveltejs/opencode",
-	"version": "0.1.2",
+	"version": "0.1.1",
 	"type": "module",
 	"license": "MIT",
 	"homepage": "https://github.com/sveltejs/mcp#readme",

packages/opencode/skills/svelte-code-writer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: svelte-code-writer
-description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
+description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
 ---
 
 # Svelte 5 Code Writer

plugins/svelte/skills/svelte-code-writer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: svelte-code-writer
-description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
+description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
 ---
 
 # Svelte 5 Code Writer