Overview | Atomicwork | Documentation

Connect Your MCP Client

The Atomicwork MCP server uses SSE (Server-Sent Events) transport and can be connected from any MCP-compatible client.

Server URL

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

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

Authentication

All requests require an API key passed in the X-Api-Key header. You can generate an API key from Settings > API Keys in your Atomicwork dashboard.

Supported Clients

Client	Transport	Config Format
Claude Code	SSE (native)	`.mcp.json` or CLI command
Claude Desktop	stdio (via mcp-remote bridge)	`claude_desktop_config.json`
Cursor	SSE (native)	`.cursor/mcp.json`
VS Code / Copilot	SSE (native)	`.vscode/mcp.json`
OpenAI Codex	SSE (native)	`~/.codex/config.toml`

Note: ChatGPT currently requires OAuth 2.1 authentication and Streamable HTTP transport, which are not yet supported by the Atomicwork MCP server. Use one of the clients above instead.

Environment Variable Interpolation

Most clients support ${env:VAR_NAME} syntax in config files so you can avoid hardcoding your API key. Set the environment variable:

$ export ATOMICWORK_API_KEY="your-api-key-here"

Then reference it in your config as ${env:ATOMICWORK_API_KEY}.