A private MCP registry your AI assistants read directly.
Atrium replaces the stale wiki page of MCP setup instructions with a curated, governed catalog that AI assistants query themselves — and hands each person install steps for their own client.
From an unmanaged sprawl of MCP servers to a governed catalog
Add the MCP servers your organization has vetted to your private catalog.
Set who can see what, and which servers require an approval request.
Employees ask their assistant what's available and get the approved catalog back.
Each person receives install instructions for their own client — no wiki required.
A per-organization catalog of approved MCP servers that any MCP-speaking client can query with a single connection.
Cursor and VS Code deeplinks, claude mcp add commands, or Claude Desktop config snippets — matched to the tool the person is actually using.
Control which servers each employee can see, and route everything else through an approval workflow instead of ad-hoc installs.
Atrium checks your managed-mcp.json and allowed-server policy and tells users whether a server is already approved.
Point Atrium at a backing source and it runs the tools server-side, so employees query the data without ever handling credentials.
Atrium instructs; it never edits config files or installs packages on anyone's machine.
Atrium is built for organizations adopting Claude Code, Cursor, and Claude Desktop at scale. Get in touch and we'll walk you through it.