docs: new sync

paoloricciuti · paoloricciuti · commit 6b5790299521 · 2025-10-03T19:54:18.000+02:00
diff --git a/apps/svelte.dev/content/docs/mcp/10-introduction/10-overview.md b/apps/svelte.dev/content/docs/mcp/10-introduction/10-overview.md
@@ -3,15 +3,18 @@ NOTE: do not edit this file, it is generated in apps/svelte.dev/scripts/sync-doc
 title: Overview
 ---
 
-The official Svelte MCP (Model Context Protocol) Server can help your LLM or Agent of choice write better Svelte code by providing it with documentation and tools to get suggestions on the generated code based on static analysis.
+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 differs based on the version of the MCP you prefer (either remote or local) and the MCP client of your choice (e.g. Claude Code, Codex CLI, GitHub Copilot etc.). Refer to our documentation to learn how to set those up [locally](./local-setup) and [remotely](./remote-setup) for the most common clients.
+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 we recommend including the following prompt in your `AGENTS.md` or `CLAUDE.md`. This will instruct the LLM on what's available and when it's appropriate to use the MCP.
+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:
@@ -39,4 +42,4 @@ 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.
+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.
diff --git a/apps/svelte.dev/content/docs/mcp/20-setup/20-local-setup.md b/apps/svelte.dev/content/docs/mcp/20-setup/20-local-setup.md
@@ -3,7 +3,7 @@ NOTE: do not edit this file, it is generated in apps/svelte.dev/scripts/sync-doc
 title: Local setup
 ---
 
-The STDIO (local) version of the MCP server is available as an `npm` package: `@sveltjs/mcp`. You can either install it globally and then reference it in your configuration or run it with `npx`.
+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
@@ -16,67 +16,63 @@ Here's how to set it up in some common MCP clients:
 To include the local MCP version in Claude Code, simply run the following command:
 
 ```bash
-claude mcp add -t stdio -s [scope] [name] npx -y @sveltejs/mcp
+claude mcp add -t stdio -s [scope] svelte npx -y @sveltejs/mcp
 ```
 
-You can choose your preferred `scope` (it must be `user`, `project` or `local`) and `name`.
+The `[scope]` must be `user`, `project` or `local`.
 
 ## Claude Desktop
 
-Open the Developer section in settings, 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:
+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": {
-		"[name]": {
+		"svelte": {
 			"command": "npx",
 			"args": ["-y", "@sveltejs/mcp"]
 		}
 	}
 }
 ```
 
-The top level must be `mcpServers` but you can choose your preferred `name`.
-
 ## Codex CLI
 
-Add the following to your `config.toml` (defaults to `~/.codex/config.toml`... refer to [the configuration documentation](https://github.com/openai/codex/blob/69cb72f8422f2aa7222bea3a6ce48fd130fa76c4/docs/config.md) for more advanced setups):
+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.name]
+[mcp_servers.svelte]
 command = "npx"
 args = ["-y", "@sveltejs/mcp"]
 ```
 
-The top level must be `mcp_server` but you can choose your preferred `name`.
-
 ## Gemini CLI
 
 To include the local MCP version in Gemini CLI, simply run the following command:
 
 ```bash
-gemini mcp add -t stdio -s [scope] [name] npx -y @sveltejs/mcp
+gemini mcp add -t stdio -s [scope] svelte npx -y @sveltejs/mcp
 ```
 
-You can choose your preferred `scope` (it must be `user`, `project` or `local`) and `name`.
+The `[scope]` must be `user`, `project` or `local`.
 
-## Opencode
+## OpenCode
 
 Run the command:
 
 ```bash
 opencode mcp add
 ```
 
-and follow the instructions, selecting Local when asked for "Select MCP server type":
+and follow the instructions, selecting 'Local' under the 'Select MCP server type' prompt:
 
 ```bash
 opencode mcp add
 
 ┌  Add MCP server
 │
 ◇  Enter MCP server name
-│  [name]
+│  svelte
 │
 ◇  Select MCP server type
 │  Local
@@ -85,20 +81,18 @@ opencode mcp add
 │  npx -y @sveltejs/mcp
 ```
 
-You can choose your preferred `name`.
+## VS Code
 
-## VSCode
-
-- Open the command Palette
+- Open the command palette
 - Select "MCP: Add Server..."
 - Select "Command (stdio)"
 - Insert `npx -y @sveltejs/mcp` in the input and press `Enter`
-- Insert your preferred name
+- 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
+- Open the command palette
 - Select "View: Open MCP Settings"
 - Click on "Add custom MCP"
 
@@ -107,16 +101,14 @@ It will open a file with your MCP servers where you can add the following config
 ```json
 {
 	"mcpServers": {
-		"[name]": {
+		"svelte": {
 			"command": "npx",
 			"args": ["-y", "@sveltejs/mcp"]
 		}
 	}
 }
 ```
 
-The top level must be `mcpServers` but you can choose your preferred `name`.
-
 ## 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.
diff --git a/apps/svelte.dev/content/docs/mcp/20-setup/30-remote-setup.md b/apps/svelte.dev/content/docs/mcp/20-setup/30-remote-setup.md
@@ -12,58 +12,56 @@ Here's how to set it up in some common MCP clients:
 To include the remote MCP version in Claude Code, simply run the following command:
 
 ```bash
-claude mcp add -t http -s [scope] [name] https://mcp.svelte.dev/mcp
+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`
-- Insert the name you prefer most
-- Insert `https://mcp.svelte.dev/mcp` as the `Remote MCP server URL`
-- Click `Add`
+- 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` (defaults to `~/.codex/config.toml`... refer to [the configuration documentation](https://github.com/openai/codex/blob/69cb72f8422f2aa7222bea3a6ce48fd130fa76c4/docs/config.md) for more advanced setups):
+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.name]
+[mcp_servers.svelte]
 url = "https://mcp.svelte.dev/mcp"
 ```
 
-To use HTTP servers in Codex you need to enable `experimental_use_rmcp_client` and the top level must be `mcp_server` but you can choose your preferred `name`.
-
 ## Gemini CLI
 
-To include the remote MCP version in Gemini CLI, simply run the following command:
+To use the remote MCP server with Gemini CLI, simply run the following command:
 
 ```bash
-gemini mcp add -t http -s [scope] [name] https://mcp.svelte.dev/mcp
+gemini 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`.
+The `[scope]` must be `user`, `project` or `local`.
 
-## Opencode
+## OpenCode
 
 Run the command:
 
 ```bash
 opencode mcp add
 ```
 
-and follow the instructions, selecting Remote when asked for "Select MCP server type":
+and follow the instructions, selecting 'Remote' under the 'Select MCP server type' prompt:
 
 ```bash
 opencode mcp add
 
 ┌  Add MCP server
 │
 ◇  Enter MCP server name
-│  [name]
+│  svelte
 │
 ◇  Select MCP server type
 │  Remote
@@ -72,11 +70,9 @@ opencode mcp add
 │  https://mcp.svelte.dev/mcp
 ```
 
-You can choose your preferred `name`.
+## VS Code
 
-## VSCode
-
-- Open the command Palette
+- 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`
@@ -85,7 +81,7 @@ You can choose your preferred `name`.
 
 ## Cursor
 
-- Open the command Palette
+- Open the command palette
 - Select "View: Open MCP Settings"
 - Click on "Add custom MCP"
 
@@ -94,15 +90,13 @@ It will open a file with your MCP servers where you can add the following config
 ```json
 {
 	"mcpServers": {
-		"[name]": {
+		"svelte": {
 			"url": "https://mcp.svelte.dev/mcp"
 		}
 	}
 }
 ```
 
-The top level must be `mcpServers` but you can choose your preferred `name`.
-
 ## 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.
diff --git a/apps/svelte.dev/content/docs/mcp/30-capabilities/10-tools.md b/apps/svelte.dev/content/docs/mcp/30-capabilities/10-tools.md
@@ -3,20 +3,20 @@ NOTE: do not edit this file, it is generated in apps/svelte.dev/scripts/sync-doc
 title: Tools
 ---
 
-This is the list of available tools provided by the MCP server. The list of tools is given to the model which can decide to call one or more of the tools during a session.
+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 and their use cases if available. The titles of the sections will be used by the LLM to get up-to-date documentation directly from the official documentation.
+Provides a list of all the available documentation sections.
 
 ## get-documentation
 
-Allows the model to get the full documentation for the requested sections. The documentation is fetched on the fly from the official Svelte documentation and it will always be up to date.
+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, the server uses the `share-with-hash` functionality of the Svelte playground to generate the correct hash on the fly (which is also why it will generate a pretty big 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).
