Install the Atmos Pro MCP server

The Atmos Pro MCP exposes your workspace's drift, deployments, workflow runs, audit log, and Repairs / Setup / Recommendations panels to any Model Context Protocol–capable LLM client. There is no API key to copy — authentication is browser-based GitHub login, and the resulting token is short-lived (≤1 hour) and revocable from Settings → MCP Clients.

Claude Code

Pick whichever you prefer — they do the same thing. A browser opens for sign-in and consent on first use.

Option 1 — Claude CLI

claude mcp add --transport http atmos-pro https://atmos-pro.com/mcp

Option 2 — Edit ~/.claude.json (global) or .mcp.json (per-project)

{
  "mcpServers": {
    "atmos-pro": {
      "type": "http",
      "url": "https://atmos-pro.com/mcp"
    }
  }
}

What happens when I install?

The client registers itself with our OAuth issuer (RFC 7591 Dynamic Client Registration).
A browser opens to atmos-pro.com. If you aren't signed in, sign in with GitHub.
Pick which workspace this client should access and which scopes to grant it.
Click Allow. The browser redirects back to the client; tokens are stored in the OS keychain.

Tokens are bound to one workspace. To switch workspaces, re-authorize. Revoking a client from Settings → MCP Clients invalidates every access and refresh token immediately.