> 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 Code

## Connect from Claude Code

Claude Code supports streamable HTTP transport natively. You can add the Atomicwork MCP server with a single CLI command, and authenticate with OAuth or a bearer token.

### Connect with OAuth

With OAuth, you never create or paste an API token. You add the server once, then authorize in your browser with your Atomicwork login.

1. Add the server without an auth header:

   ```bash
   claude mcp add --transport http Atomicwork https://<your-subdomain>.atomicwork.com/mcp
   ```

2. Run `/mcp` in Claude Code. Atomicwork appears with the status **needs authentication**.

3. Select **Atomicwork** and choose to authenticate. Claude Code opens a browser tab.

4. Sign in to Atomicwork and approve access.

5. The tab shows **Authentication successful**. Return to Claude Code, which reports **Reconnected** and loads the tools.

### Connect with a bearer token

If you'd rather use an API token, pass it in the `Authorization` header when you add the server.

```bash
claude mcp add --transport http Atomicwork \
  https://<your-subdomain>.atomicwork.com/mcp \
  --header "Authorization: Bearer aw_xxx"
```

#### Configuration File

The command above writes to `~/.claude.json`. You can also create a project-scoped `.mcp.json` in your repo root:

```json
{
  "mcpServers": {
    "Atomicwork": {
      "type": "http",
      "url": "https://<your-subdomain>.atomicwork.com/mcp",
      "headers": {
        "Authorization": "Bearer ${ATOMICWORK_TOKEN}"
      }
    }
  }
}
```

Avoid committing real tokens to version control — for project-scoped configs, reference an environment variable as shown above rather than hardcoding `aw_xxx`.

### Scopes

| Scope   | Flag                      | Location                                           | Shared via VCS? |
| ------- | ------------------------- | -------------------------------------------------- | --------------- |
| Local   | `--scope local` (default) | `~/.claude.json`, under the current project's path | No              |
| Project | `--scope project`         | `.mcp.json`                                        | Yes             |
| User    | `--scope user`            | `~/.claude.json`                                   | No              |

### Verify Connection

Inside a Claude Code session, run:

```
/mcp
```

You should see `Atomicwork` listed with its available tools.