Atrium documentation
Atrium runs your connectors server-side and scopes them per client. Your team adds one endpoint to their assistant; which accounts they can reach through it is decided by you.
Two kinds of capability
A single connection exposes two things that are easy to confuse. Knowing which is which explains most of Atrium’s behavior.
1. Hosted connector tools
Integrations Atrium runs for you. They appear directly in the tool list, named <connector>_<action>, and the assistant calls them like any other tool. You never install or approve these through the meta-tools below, and they never appear in the catalog.
2. Catalog discovery meta-tools
list_available_servers, get_server_details, get_install_instructions, check_install_status, request_approval, and check_policy_status. These help a user discover and install separate external MCP servers into their own client.
Your endpoint
One Streamable-HTTP MCP endpoint per organization. Authenticate with an organization API key (sk_org_…) for server-to-server callers, or over OAuth for desktop and web clients.
https://atrium.savantly.cloud/api/mcp/{org-slug}Keep reading
- Connect a clientAdd Atrium to Claude Code or Claude Desktop, with an API key or over OAuth.
- Hosted connectorsWhat Postgres, Google Analytics 4, and Search Console each contribute to your tool list.
- Roles & governanceEntitlements, server-bound scope, approval requests, and managed-policy awareness.
- SecurityWhere credentials live, what leaves the server, and what Atrium deliberately will not do.