<!-- source: https://vectoralix.com/docs/clients/claude-desktop | service: Vectoralix | format: markdown twin auto-generated from the canonical HTML page -->

Client Integrations

#  Claude Desktop 

 Wire a Vectoralix MCP server into Claude Desktop on macOS or Windows. Once configured, the server's tools surface in the composer's tools tray and Claude can invoke them on demand during a chat.

  **Prefer one-click install?:** Download a .mcpb bundle from the dashboard instead — Claude Desktop installs it with a double-click and no JSON editing. See [Claude Desktop — One-Click Install (Bundle)](https://vectoralix.com/docs/clients/desktop-bundle). This page is the manual JSON-edit fallback.

 

## Before you start

- Claude Desktop installed and signed in.
- A Vectoralix MCP server you have permission to view, with at least one published version.
- The server's endpoint URL copied from the Connection panel, and — for private servers — the endpoint token.
 
## Locate the Claude Desktop config file

 Claude Desktop reads MCP server definitions from a JSON config file under your user profile. Create the file if it does not exist; an empty Claude Desktop install does not ship one by default.

    Operating system Config file path     macOS `~/Library/Application Support/Claude/claude_desktop_config.json`   Windows `%APPDATA%\Claude\claude_desktop_config.json`   ## Add an mcpServers entry

 Add an entry under mcpServers keyed by a friendly name of your choice. The shape Claude Desktop expects is a JSON object with the connection URL and, for private servers, an Authorization header carrying the endpoint token. The exact field names follow Anthropic's Claude Desktop documentation — verify them against the latest published config schema before pasting into production.

### Public server

```
{
  "mcpServers": {
    "vectoralix-docs": {
      "url": "https://vectoralix.com/mcp/<serverUid>"
    }
  }
}
```

### Private server

```
{
  "mcpServers": {
    "vectoralix-docs": {
      "url": "https://vectoralix.com/mcp/<serverUid>",
      "headers": {
        "Authorization": "Bearer <endpoint-token>"
      }
    }
  }
}
```

 Replace &lt;serverUid&gt; and &lt;endpoint-token&gt; with the literal values copied from the Vectoralix dashboard. Keep the file as well-formed JSON — a single trailing comma will silently break the integration.

## Restart and verify

1. Quit Claude Desktop completely (not just close the window) and reopen it so the config file is re-read.
2. Open the tools tray in the composer; the friendly name you used as the mcpServers key should appear with the count of tools loaded.
3. Send a prompt that exercises one of the tools — for a File Search server, ask "Search my docs for X" and confirm the response cites results.
 
## Troubleshooting

- Server name not appearing — JSON syntax error. Validate the config in any JSON linter before retrying. Claude Desktop tends to fail silently on parse errors.
- Tools appear but every call fails with 401 — the Authorization header is missing or stale; re-copy the endpoint token from the dashboard.
- Server appears but lists zero tools — the server has no active version, or the version has no enabled tools. Publish a version with at least one enabled tool attached.
- Calls succeed in the Vectoralix Playground but not from Claude Desktop — confirm the URL has the /mcp/ prefix and the serverUid matches exactly.
 
 **Test in the Playground first:** If the Vectoralix Playground can connect, the URL and token are correct. Anything that fails afterwards is local to Claude Desktop's config or restart cycle.