> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Desktop

> Set up and use the OpenCX MCP server in Claude Desktop — config file locations, restart behavior, and multi-server setup.

Claude Desktop supports <Tooltip tip="An open standard that lets AI assistants interact with external tools and data sources.">MCP</Tooltip> servers through a JSON config file. The file location depends on your operating system.

<Warning>
  Claude Desktop must be **fully restarted** (quit and reopen, not just start a
  new conversation) after any config change. This is the most common setup
  issue.
</Warning>

## Setup

<Steps>
  <Step title="Open the config file">
    The config file location depends on your OS:

    <Tabs>
      <Tab title="macOS">
        ```
        ~/Library/Application Support/Claude/claude_desktop_config.json
        ```

        Open it in your editor, or run:

        ```bash theme={"dark"}
        open ~/Library/Application\ Support/Claude/claude_desktop_config.json
        ```
      </Tab>

      <Tab title="Windows">
        ```
        %APPDATA%\Claude\claude_desktop_config.json
        ```

        Open it in your editor, or press `Win+R` and paste the path above.
      </Tab>

      <Tab title="Linux">
        ```
        ~/.config/Claude/claude_desktop_config.json
        ```
      </Tab>
    </Tabs>

    If the file doesn't exist, create it.
  </Step>

  <Step title="Add the OpenCX server">
    Paste this into your config file:

    ```json theme={"dark"}
    {
      "mcpServers": {
        "opencx": {
          "command": "npx",
          "args": ["-y", "@opencx/mcp"],
          "env": {
            "OPENCX_API_KEY": "your-api-key-here"
          }
        }
      }
    }
    ```

    Replace `your-api-key-here` with your [OpenCX API key](https://platform.open.cx/settings/access).

    <Tip>
      To use the [hosted endpoint](/mcp/install#remote-server-no-install) instead of running the server locally, bridge it with [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) (Claude Desktop's connector UI doesn't support custom auth headers):

      ```json theme={"dark"}
      {
        "mcpServers": {
          "opencx": {
            "command": "npx",
            "args": [
              "-y",
              "mcp-remote",
              "https://api.open.cx/mcp",
              "--header",
              "Authorization: Bearer your-api-key-here"
            ]
          }
        }
      }
      ```
    </Tip>
  </Step>

  <Step title="Restart Claude Desktop">
    **Fully quit** Claude Desktop (not just close the window) and reopen it. On
    macOS, use `Cmd+Q`. On Windows, right-click the system tray icon and select
    **Quit**.
  </Step>

  <Step title="Verify">
    Look for the **hammer icon** in the chat input area. Click it to see connected MCP servers and available tools. Then ask: *"List my recent chat sessions."*
  </Step>
</Steps>

## The MCP Indicator

Once connected, a **hammer icon** appears next to the chat input. Click it to see:

* Which MCP servers are connected
* How many tools are available
* Individual tool names (click to expand)

If the hammer icon doesn't appear, the config file isn't being read. Double-check the file path and restart Claude Desktop.

## Multiple MCP Servers

Add other MCP servers alongside OpenCX in the same `mcpServers` object:

```json theme={"dark"}
{
  "mcpServers": {
    "opencx": {
      "command": "npx",
      "args": ["-y", "@opencx/mcp"],
      "env": {
        "OPENCX_API_KEY": "your-opencx-key"
      }
    },
    "another-server": {
      "command": "npx",
      "args": ["-y", "@another/mcp-server"],
      "env": {
        "API_KEY": "your-other-key"
      }
    }
  }
}
```

Each server runs as a separate process. Claude Desktop makes tools from all connected servers available in every conversation.

## Common Issues

| Symptom                          | Fix                                                                                                              |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Hammer icon missing              | Check config file path and JSON syntax. Restart Claude Desktop fully.                                            |
| Tools appear but fail with 401   | API key is invalid or revoked. Generate a new one in your [dashboard](https://platform.open.cx/settings/access). |
| "Server disconnected" after idle | Claude Desktop may stop idle MCP servers. Start a new conversation to reconnect.                                 |

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Claude Code" icon="terminal" href="/mcp/clients/claude-code">
    CLI-based MCP setup in the same Claude family
  </Card>

  <Card title="Get Started" icon="download" href="/mcp/install">
    API key setup and all client configs
  </Card>

  <Card title="Prompt Library" icon="message" href="/mcp/prompts">
    Ready-to-use prompts by domain
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/mcp/troubleshooting">
    Common issues and fixes
  </Card>
</CardGroup>