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

# Claude Desktop

> Add Yambr as an MCP tool server in Claude Desktop — one JSON entry.

Claude Desktop speaks MCP over Streamable HTTP natively. Add one entry to `claude_desktop_config.json` and the Computer Use tools appear next to your other MCP servers.

## Managed Yambr

```json theme={null}
{
  "mcpServers": {
    "yambr-computer-use": {
      "url": "https://api.yambr.com/mcp/computer_use",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer sk-yambr-...",
        "X-Chat-Id": "claude-desktop"
      }
    }
  }
}
```

Get the key at [app.yambr.com](https://app.yambr.com/). Use a stable `X-Chat-Id` for a persistent sandbox; rotate it to start fresh.

Claude Desktop uses your Anthropic subscription for the model — we only provide the tools. [Why MCP-only →](/platform/access-model)

## Self-hosted

```json theme={null}
{
  "mcpServers": {
    "computer-use": {
      "url": "http://localhost:8081/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer <MCP_API_KEY>",
        "X-Chat-Id": "desktop-session"
      }
    }
  }
}
```

## Config file location

* macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
* Windows: `%APPDATA%\Claude\claude_desktop_config.json`

Restart Claude Desktop. You should see the Computer Use tools in the tool picker.

## Single-user mode (self-hosted)

Since Claude Desktop is one user, flip the self-hosted server to single-user mode so you don't have to manage `X-Chat-Id`:

```bash theme={null}
echo "SINGLE_USER_MODE=true" >> .env
docker compose restart computer-use-server
```

Every request then reuses the same sandbox; `X-Chat-Id` can be anything. Managed Yambr runs strict multi-user — always pass a meaningful `X-Chat-Id`.

## Headers reference

| Header          | Required          | Purpose                                                    |
| --------------- | ----------------- | ---------------------------------------------------------- |
| `Authorization` | Yes               | `Bearer <yambr-key>` or `Bearer <MCP_API_KEY>`             |
| `X-Chat-Id`     | Yes (strict mode) | Session identifier → one sandbox per id                    |
| `X-User-Email`  | No                | Per-user skills / PAT lookup                               |
| `X-User-Name`   | No                | Display name (URL-encoded)                                 |
| `X-MCP-Servers` | No                | Comma-separated MCP server names passed to the `sub_agent` |

## Related

* [MCP API reference](/api-reference/introduction) — headers, endpoints, tool list
* [Access model](/platform/access-model) — why Yambr is MCP-only
* [Self-hosting quickstart](/install/quickstart) — stand up your own server