@commercetools/nimbus-mcp 0.1.0 → 2.11.0

package/data/docs/routes/home-getting-started-mcp-server-overview.json

@@ -0,0 +1,139 @@
+{
+  "meta": {
+    "id": "Home-MCP-Overview",
+    "title": "MCP Server Overview",
+    "description": "What the Nimbus MCP server is, what it enables, and which AI assistants it supports",
+    "order": 5,
+    "repoPath": "packages/nimbus/src/docs/home-mcp-server-overview.mdx",
+    "menu": [
+      "Home",
+      "Getting Started",
+      "MCP Server Overview"
+    ],
+    "route": "home/getting-started/mcp-server-overview",
+    "tags": [
+      "mcp",
+      "ai",
+      "developer-tools"
+    ],
+    "toc": [
+      {
+        "value": "What Is MCP?",
+        "href": "#what-is-mcp",
+        "depth": 2,
+        "numbering": [
+          1,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "What It Enables",
+        "href": "#what-it-enables",
+        "depth": 2,
+        "numbering": [
+          1,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Available Tools",
+        "href": "#available-tools",
+        "depth": 2,
+        "numbering": [
+          1,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Supported AI Assistants",
+        "href": "#supported-ai-assistants",
+        "depth": 2,
+        "numbering": [
+          1,
+          4
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Package Details",
+        "href": "#package-details",
+        "depth": 2,
+        "numbering": [
+          1,
+          5
+        ],
+        "parent": "root"
+      }
+    ],
+    "icon": "SmartToy",
+    "layout": "app-frame",
+    "tabs": [
+      {
+        "key": "overview",
+        "title": "Overview",
+        "order": 0
+      }
+    ]
+  },
+  "mdx": "\n# MCP Server Overview\n\nIf you use an AI coding assistant (Claude, Copilot, Cursor, etc.), the Nimbus\nMCP server lets it understand the design system automatically — no more pasting\ndocs into every prompt.\n\nThe **Nimbus MCP Server** (`@commercetools/nimbus-mcp`) exposes component\ndocumentation, design tokens, and icons to AI assistants through the\n[Model Context Protocol (MCP)](https://modelcontextprotocol.io/), so they can\nproduce code that follows Nimbus conventions out of the box.\n\n## What Is MCP?\n\nThe **Model Context Protocol** is an open standard that lets AI assistants call\nexternal tools. It works like a simple request/response message format: an MCP\n_server_ advertises a set of tools, and an MCP _client_ (the AI assistant)\ndiscovers and invokes them as needed during a conversation.\n\nThe Nimbus MCP server runs locally on your machine as a subprocess of the AI\nassistant — no network deployment or API keys required.\n\n## What It Enables\n\nWith the MCP server running, an AI assistant can:\n\n- **Look up component APIs** — props, variants, slots, and usage examples for\n  any Nimbus component or pattern\n- **Query design tokens** — colors, spacing, typography, shadows, and other\n  token values by name or category\n- **Search documentation** — full-text search across all Nimbus docs including\n  guidelines and accessibility views\n- **Find icons** — fuzzy-search the icon catalog by name or keyword\n- **List components** — browse all available components filtered by category\n- **Migrate from UI Kit** — get migration mappings from `@commercetools-uikit`\n  components to their Nimbus equivalents\n\nThis means you can ask your AI assistant questions like _\"build a form with\nNimbus components\"_ or _\"what spacing tokens are available?\"_ and it will have\naccurate, up-to-date answers pulled directly from the design system.\n\n## Available Tools\n\nThe server exposes the following tools:\n\n| Tool               | Description                                                                    |\n| ------------------ | ------------------------------------------------------------------------------ |\n| `list_components`  | Returns Nimbus components, optionally filtered by subcategory or fuzzy search  |\n| `get_component`    | Returns detailed info about a component — metadata, props, styling config, and docs |\n| `get_tokens`       | Returns design tokens, optionally filtered by category or searched by name     |\n| `search_docs`      | Full-text search across all Nimbus documentation pages                         |\n| `search_icons`     | Fuzzy-search the icon catalog by name or keyword                               |\n| `migrate_from_uikit` | Returns migration mappings from UI Kit components to Nimbus equivalents       |\n\n## Supported AI Assistants\n\nThe Nimbus MCP server works with any MCP-compatible client. Tested assistants\ninclude:\n\n| Assistant           | Configuration file                               |\n| ------------------- | ------------------------------------------------ |\n| **Claude Code**     | `~/.claude/mcp.json` or project `.mcp.json`      |\n| **Claude Desktop**  | App settings or `claude_desktop_config.json`      |\n| **VS Code Copilot** | `.vscode/mcp.json` in workspace                  |\n| **Cursor**          | `.cursor/mcp.json` in workspace                  |\n| **Windsurf**        | `.windsurf/mcp.json` in workspace                |\n\n> See the [Setup guide](/home/getting-started/mcp-server-setup) for step-by-step\n> configuration instructions for each assistant.\n\n## Package Details\n\n- **Package name:** `@commercetools/nimbus-mcp`\n- **Source:** `packages/nimbus-mcp/` in the Nimbus monorepo\n",
+  "views": {
+    "overview": {
+      "mdx": "\n# MCP Server Overview\n\nIf you use an AI coding assistant (Claude, Copilot, Cursor, etc.), the Nimbus\nMCP server lets it understand the design system automatically — no more pasting\ndocs into every prompt.\n\nThe **Nimbus MCP Server** (`@commercetools/nimbus-mcp`) exposes component\ndocumentation, design tokens, and icons to AI assistants through the\n[Model Context Protocol (MCP)](https://modelcontextprotocol.io/), so they can\nproduce code that follows Nimbus conventions out of the box.\n\n## What Is MCP?\n\nThe **Model Context Protocol** is an open standard that lets AI assistants call\nexternal tools. It works like a simple request/response message format: an MCP\n_server_ advertises a set of tools, and an MCP _client_ (the AI assistant)\ndiscovers and invokes them as needed during a conversation.\n\nThe Nimbus MCP server runs locally on your machine as a subprocess of the AI\nassistant — no network deployment or API keys required.\n\n## What It Enables\n\nWith the MCP server running, an AI assistant can:\n\n- **Look up component APIs** — props, variants, slots, and usage examples for\n  any Nimbus component or pattern\n- **Query design tokens** — colors, spacing, typography, shadows, and other\n  token values by name or category\n- **Search documentation** — full-text search across all Nimbus docs including\n  guidelines and accessibility views\n- **Find icons** — fuzzy-search the icon catalog by name or keyword\n- **List components** — browse all available components filtered by category\n- **Migrate from UI Kit** — get migration mappings from `@commercetools-uikit`\n  components to their Nimbus equivalents\n\nThis means you can ask your AI assistant questions like _\"build a form with\nNimbus components\"_ or _\"what spacing tokens are available?\"_ and it will have\naccurate, up-to-date answers pulled directly from the design system.\n\n## Available Tools\n\nThe server exposes the following tools:\n\n| Tool               | Description                                                                    |\n| ------------------ | ------------------------------------------------------------------------------ |\n| `list_components`  | Returns Nimbus components, optionally filtered by subcategory or fuzzy search  |\n| `get_component`    | Returns detailed info about a component — metadata, props, styling config, and docs |\n| `get_tokens`       | Returns design tokens, optionally filtered by category or searched by name     |\n| `search_docs`      | Full-text search across all Nimbus documentation pages                         |\n| `search_icons`     | Fuzzy-search the icon catalog by name or keyword                               |\n| `migrate_from_uikit` | Returns migration mappings from UI Kit components to Nimbus equivalents       |\n\n## Supported AI Assistants\n\nThe Nimbus MCP server works with any MCP-compatible client. Tested assistants\ninclude:\n\n| Assistant           | Configuration file                               |\n| ------------------- | ------------------------------------------------ |\n| **Claude Code**     | `~/.claude/mcp.json` or project `.mcp.json`      |\n| **Claude Desktop**  | App settings or `claude_desktop_config.json`      |\n| **VS Code Copilot** | `.vscode/mcp.json` in workspace                  |\n| **Cursor**          | `.cursor/mcp.json` in workspace                  |\n| **Windsurf**        | `.windsurf/mcp.json` in workspace                |\n\n> See the [Setup guide](/home/getting-started/mcp-server-setup) for step-by-step\n> configuration instructions for each assistant.\n\n## Package Details\n\n- **Package name:** `@commercetools/nimbus-mcp`\n- **Source:** `packages/nimbus-mcp/` in the Nimbus monorepo\n",
+      "toc": [
+        {
+          "value": "What Is MCP?",
+          "href": "#what-is-mcp",
+          "depth": 2,
+          "numbering": [
+            1,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "What It Enables",
+          "href": "#what-it-enables",
+          "depth": 2,
+          "numbering": [
+            1,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Available Tools",
+          "href": "#available-tools",
+          "depth": 2,
+          "numbering": [
+            1,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Supported AI Assistants",
+          "href": "#supported-ai-assistants",
+          "depth": 2,
+          "numbering": [
+            1,
+            4
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Package Details",
+          "href": "#package-details",
+          "depth": 2,
+          "numbering": [
+            1,
+            5
+          ],
+          "parent": "root"
+        }
+      ]
+    }
+  }
+}

package/data/docs/routes/home-getting-started-mcp-server-setup.json

@@ -0,0 +1,316 @@
+{
+  "meta": {
+    "id": "Home-MCP-Setup",
+    "title": "MCP Server Setup",
+    "description": "Install and configure the Nimbus MCP server for your AI assistant",
+    "order": 6,
+    "repoPath": "packages/nimbus/src/docs/home-mcp-server-setup.mdx",
+    "menu": [
+      "Home",
+      "Getting Started",
+      "MCP Server Setup"
+    ],
+    "route": "home/getting-started/mcp-server-setup",
+    "tags": [
+      "mcp",
+      "ai",
+      "developer-tools",
+      "setup"
+    ],
+    "toc": [
+      {
+        "value": "Prerequisites",
+        "href": "#prerequisites",
+        "depth": 2,
+        "numbering": [
+          1,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "How It Works",
+        "href": "#how-it-works",
+        "depth": 2,
+        "numbering": [
+          1,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Installation",
+        "href": "#installation",
+        "depth": 2,
+        "numbering": [
+          1,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Quick Start (npx — recommended)",
+        "href": "#quick-start-npx--recommended",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Monorepo (contributors)",
+        "href": "#monorepo-contributors",
+        "depth": 3,
+        "numbering": [
+          1,
+          3,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Configuration by Assistant",
+        "href": "#configuration-by-assistant",
+        "depth": 2,
+        "numbering": [
+          1,
+          4
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Claude Code",
+        "href": "#claude-code",
+        "depth": 3,
+        "numbering": [
+          1,
+          4,
+          1
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Claude Desktop",
+        "href": "#claude-desktop",
+        "depth": 3,
+        "numbering": [
+          1,
+          4,
+          2
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "VS Code (Copilot)",
+        "href": "#vs-code-copilot",
+        "depth": 3,
+        "numbering": [
+          1,
+          4,
+          3
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Cursor",
+        "href": "#cursor",
+        "depth": 3,
+        "numbering": [
+          1,
+          4,
+          4
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Windsurf",
+        "href": "#windsurf",
+        "depth": 3,
+        "numbering": [
+          1,
+          4,
+          5
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Verify the Setup",
+        "href": "#verify-the-setup",
+        "depth": 2,
+        "numbering": [
+          1,
+          5
+        ],
+        "parent": "root"
+      },
+      {
+        "value": "Troubleshooting",
+        "href": "#troubleshooting",
+        "depth": 3,
+        "numbering": [
+          1,
+          5,
+          1
+        ],
+        "parent": "root"
+      }
+    ],
+    "icon": "Build",
+    "layout": "app-frame",
+    "tabs": [
+      {
+        "key": "overview",
+        "title": "Overview",
+        "order": 0
+      }
+    ]
+  },
+  "mdx": "\n# MCP Server Setup\n\nThis guide walks through installing the Nimbus MCP server and configuring it for\nyour AI assistant. Setup takes about two minutes.\n\n## Prerequisites\n\n- **Node.js** v18 or later (includes `npx`)\n- An AI assistant that supports MCP (see\n  [supported assistants](/home/getting-started/mcp-server-overview))\n\n## How It Works\n\nYou don't run the MCP server yourself. Instead, you add a small JSON config to\nyour AI assistant telling it _how_ to start the server. The assistant launches\nthe server automatically when a session begins and communicates with it behind\nthe scenes.\n\nAll of the configuration snippets below follow this pattern.\n\n## Installation\n\n### Quick Start (npx — recommended)\n\nThe simplest option. Your assistant runs `npx` to pull the latest published\nversion on each session start — no local install needed.\n\nThe `-y` flag in the snippets below tells npx to skip the install confirmation\nprompt so the server starts without user interaction.\n\n### Monorepo (contributors)\n\nIf you're developing inside the Nimbus monorepo, the MCP server is already\navailable as a workspace package. Build it once:\n\n```bash\npnpm --filter @commercetools/nimbus-mcp build\n```\n\nThen use this server entry in place of the npx snippets below:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"node\",\n      \"args\": [\"packages/nimbus-mcp/dist/index.js\"]\n    }\n  }\n}\n```\n\n## Configuration by Assistant\n\nEach AI assistant reads MCP server configuration from a JSON file. Add the\n`nimbus` entry to the appropriate file for your tool.\n\n### Claude Code\n\nAdd to your project's `.mcp.json` so every team member on the repo gets the\nserver automatically, or to `~/.claude/mcp.json` to enable it across all your\nprojects:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nClaude Code discovers the server automatically on the next session start.\n\n### Claude Desktop\n\nOpen **Settings → Developer → Edit Config**, or edit the config file directly:\n\n- **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`\n- **Windows:** `%APPDATA%\\Claude\\claude_desktop_config.json`\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nRestart Claude Desktop after saving.\n\n### VS Code (Copilot)\n\nCreate or edit `.vscode/mcp.json` in your workspace root.\n\n> **Note:** VS Code uses `\"servers\"` as the top-level key, not `\"mcpServers\"`\n> like the other assistants.\n\n```json\n{\n  \"servers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nMCP support is built into VS Code 1.99+. Open the Copilot chat panel — if the\nserver is configured correctly, Copilot will discover it automatically.\n\n### Cursor\n\nCreate or edit `.cursor/mcp.json` in your workspace root:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nCursor discovers the server on the next composer session.\n\n### Windsurf\n\nCreate or edit `.windsurf/mcp.json` in your workspace root:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nWindsurf picks up new servers automatically.\n\n## Verify the Setup\n\nAfter saving the configuration, open a new chat session in your assistant and\nask:\n\n> _\"List all available Nimbus components\"_\n\nThe assistant should call the `list_components` tool and return a list of\ncomponent names and descriptions. If this works, the MCP server is connected\nand ready to use.\n\nYou can also try more specific queries:\n\n- _\"What props does the Button component accept?\"_\n- _\"What spacing tokens are available in Nimbus?\"_\n- _\"Find an icon for a shopping cart\"_\n- _\"How do I migrate PrimaryButton from UI Kit to Nimbus?\"_\n\n### Troubleshooting\n\n| Symptom                            | Likely cause                                  | Fix                                                          |\n| ---------------------------------- | --------------------------------------------- | ------------------------------------------------------------ |\n| Assistant doesn't see Nimbus tools | Config file not found or malformed JSON        | Check file path and validate JSON syntax                     |\n| `npx` command not found            | Node.js not on the assistant's PATH            | Ensure `node` (v18+) and `npx` are available in your shell   |\n| Tools return \"data not found\"      | Monorepo users: package not built              | Run `pnpm build` from the repo root (npx users are unaffected) |\n| Stale component data               | Using an older cached npx version              | Run `npx @commercetools/nimbus-mcp@latest` to clear cache    |\n",
+  "views": {
+    "overview": {
+      "mdx": "\n# MCP Server Setup\n\nThis guide walks through installing the Nimbus MCP server and configuring it for\nyour AI assistant. Setup takes about two minutes.\n\n## Prerequisites\n\n- **Node.js** v18 or later (includes `npx`)\n- An AI assistant that supports MCP (see\n  [supported assistants](/home/getting-started/mcp-server-overview))\n\n## How It Works\n\nYou don't run the MCP server yourself. Instead, you add a small JSON config to\nyour AI assistant telling it _how_ to start the server. The assistant launches\nthe server automatically when a session begins and communicates with it behind\nthe scenes.\n\nAll of the configuration snippets below follow this pattern.\n\n## Installation\n\n### Quick Start (npx — recommended)\n\nThe simplest option. Your assistant runs `npx` to pull the latest published\nversion on each session start — no local install needed.\n\nThe `-y` flag in the snippets below tells npx to skip the install confirmation\nprompt so the server starts without user interaction.\n\n### Monorepo (contributors)\n\nIf you're developing inside the Nimbus monorepo, the MCP server is already\navailable as a workspace package. Build it once:\n\n```bash\npnpm --filter @commercetools/nimbus-mcp build\n```\n\nThen use this server entry in place of the npx snippets below:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"node\",\n      \"args\": [\"packages/nimbus-mcp/dist/index.js\"]\n    }\n  }\n}\n```\n\n## Configuration by Assistant\n\nEach AI assistant reads MCP server configuration from a JSON file. Add the\n`nimbus` entry to the appropriate file for your tool.\n\n### Claude Code\n\nAdd to your project's `.mcp.json` so every team member on the repo gets the\nserver automatically, or to `~/.claude/mcp.json` to enable it across all your\nprojects:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nClaude Code discovers the server automatically on the next session start.\n\n### Claude Desktop\n\nOpen **Settings → Developer → Edit Config**, or edit the config file directly:\n\n- **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`\n- **Windows:** `%APPDATA%\\Claude\\claude_desktop_config.json`\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nRestart Claude Desktop after saving.\n\n### VS Code (Copilot)\n\nCreate or edit `.vscode/mcp.json` in your workspace root.\n\n> **Note:** VS Code uses `\"servers\"` as the top-level key, not `\"mcpServers\"`\n> like the other assistants.\n\n```json\n{\n  \"servers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nMCP support is built into VS Code 1.99+. Open the Copilot chat panel — if the\nserver is configured correctly, Copilot will discover it automatically.\n\n### Cursor\n\nCreate or edit `.cursor/mcp.json` in your workspace root:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nCursor discovers the server on the next composer session.\n\n### Windsurf\n\nCreate or edit `.windsurf/mcp.json` in your workspace root:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@commercetools/nimbus-mcp\"]\n    }\n  }\n}\n```\n\nWindsurf picks up new servers automatically.\n\n## Verify the Setup\n\nAfter saving the configuration, open a new chat session in your assistant and\nask:\n\n> _\"List all available Nimbus components\"_\n\nThe assistant should call the `list_components` tool and return a list of\ncomponent names and descriptions. If this works, the MCP server is connected\nand ready to use.\n\nYou can also try more specific queries:\n\n- _\"What props does the Button component accept?\"_\n- _\"What spacing tokens are available in Nimbus?\"_\n- _\"Find an icon for a shopping cart\"_\n- _\"How do I migrate PrimaryButton from UI Kit to Nimbus?\"_\n\n### Troubleshooting\n\n| Symptom                            | Likely cause                                  | Fix                                                          |\n| ---------------------------------- | --------------------------------------------- | ------------------------------------------------------------ |\n| Assistant doesn't see Nimbus tools | Config file not found or malformed JSON        | Check file path and validate JSON syntax                     |\n| `npx` command not found            | Node.js not on the assistant's PATH            | Ensure `node` (v18+) and `npx` are available in your shell   |\n| Tools return \"data not found\"      | Monorepo users: package not built              | Run `pnpm build` from the repo root (npx users are unaffected) |\n| Stale component data               | Using an older cached npx version              | Run `npx @commercetools/nimbus-mcp@latest` to clear cache    |\n",
+      "toc": [
+        {
+          "value": "Prerequisites",
+          "href": "#prerequisites",
+          "depth": 2,
+          "numbering": [
+            1,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "How It Works",
+          "href": "#how-it-works",
+          "depth": 2,
+          "numbering": [
+            1,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Installation",
+          "href": "#installation",
+          "depth": 2,
+          "numbering": [
+            1,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Quick Start (npx — recommended)",
+          "href": "#quick-start-npx--recommended",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Monorepo (contributors)",
+          "href": "#monorepo-contributors",
+          "depth": 3,
+          "numbering": [
+            1,
+            3,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Configuration by Assistant",
+          "href": "#configuration-by-assistant",
+          "depth": 2,
+          "numbering": [
+            1,
+            4
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Claude Code",
+          "href": "#claude-code",
+          "depth": 3,
+          "numbering": [
+            1,
+            4,
+            1
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Claude Desktop",
+          "href": "#claude-desktop",
+          "depth": 3,
+          "numbering": [
+            1,
+            4,
+            2
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "VS Code (Copilot)",
+          "href": "#vs-code-copilot",
+          "depth": 3,
+          "numbering": [
+            1,
+            4,
+            3
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Cursor",
+          "href": "#cursor",
+          "depth": 3,
+          "numbering": [
+            1,
+            4,
+            4
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Windsurf",
+          "href": "#windsurf",
+          "depth": 3,
+          "numbering": [
+            1,
+            4,
+            5
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Verify the Setup",
+          "href": "#verify-the-setup",
+          "depth": 2,
+          "numbering": [
+            1,
+            5
+          ],
+          "parent": "root"
+        },
+        {
+          "value": "Troubleshooting",
+          "href": "#troubleshooting",
+          "depth": 3,
+          "numbering": [
+            1,
+            5,
+            1
+          ],
+          "parent": "root"
+        }
+      ]
+    }
+  }
+}