Overview

Connect Your MCP Client

The Atomicwork MCP server uses streamable HTTP transport and can be connected from any MCP-compatible client.

Server URL

https://<your-subdomain>.atomicwork.com/mcp

Replace <your-subdomain> with your Atomicwork tenant subdomain.

Authentication

The Atomicwork MCP server supports two ways to authenticate:

• OAuth (Claude Code and Codex): Add the server, then authorize in your browser with your Atomicwork login. There’s no token to create and no client-side setup. See Connect using OAuth for the steps.
• Bearer token (all other clients): Pass a public API token in the Authorization header — for example, Authorization: Bearer aw_xxx. To generate a token, click your profile icon, then select Public API token.

Supported Clients

Keeping Your Token Out of Config Files

Most clients can read your token from outside the config file, so you don’t have to hardcode it. The syntax differs by client:

For the environment-variable options, set the variable in your shell first:

export ATOMICWORK_TOKEN="aw_xxx"

See each client’s page for the full configuration.