> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://support.atomicwork.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://support.atomicwork.com/_mcp/server.

# Claude Desktop

## Connect from Claude Desktop

Claude Desktop's custom connectors support remote MCP servers only with OAuth sign-in, so they can't send an Atomicwork bearer token. Use the `mcp-remote` bridge instead, which runs locally and forwards calls to the Atomicwork endpoint with your token.

### Configuration

Edit your Claude Desktop config file:

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

Add the following:

```json
{
  "mcpServers": {
    "Atomicwork": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://<your-subdomain>.atomicwork.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer aw_xxx"
      }
    }
  }
}
```

Keep the `--header` argument exactly as shown, with no space after `Authorization:`. `mcp-remote` fills in `${AUTH_HEADER}` from the `env` block. Keeping the token out of `args` avoids a known issue where Claude Desktop on Windows doesn't escape spaces in arguments, which breaks the header.

If you already have an `mcpServers` block, append the `Atomicwork` entry to it — do not replace the entire block.

### Prerequisites

* **Node.js** (v18+) must be installed and `npx` available on your PATH. Check with `node --version`.
* The `mcp-remote` package is downloaded automatically by `npx` on first use.

### After Configuration

Fully quit and relaunch Claude Desktop (not just close the window) for the changes to take effect. The Atomicwork tools will appear in the tool picker when starting a new conversation.