AtriumSign in

One gateway to everything your company runs on

Connect your systems once. Every AI your team uses gets them.

Atrium sits between the tools your company runs on and the AI your team already works in. Connect a system once and it turns up in Claude, Cursor and ChatGPT — for the people who should have it, and nobody else.

Sign in
YOUR SYSTEMSSales & CRMDatabasesEmailCalendarsDocumentsATRIUMWHERE YOUR TEAM ALREADY WORKSClaude CodeClaude DesktopCursorChatGPTAnything else

What you can connect

12 categories · 2 live today

Start with what you already run. Add the rest as you go.

Each system is connected once, by someone who has the right to connect it. After that it is simply there — nobody on your team pastes an API key into anything, and there is nothing to re-do when someone joins or leaves.

Two are connected today. The rest are honestly marked: they are the shape of what Atrium is built to sit in front of, not a list of partners. And the list is not a menu — anything with an API can be added, including the services you wrote yourself.

Pipedrive CRM

Connected

Deals, contacts and activity from the sales pipeline.

6 tools

Supabase Management API

Connected

Projects, schemas and read-only queries against Supabase.

4 tools

On the roadmap

EmailCalendarsDocumentsFiles & storageTicketingChatAnalyticsPaymentsCode hostingHR & people

Bring your own

not just catalogue apps

The systems you built yourself count too.

Most of what a company runs on is not on anybody’s integration list — it is an internal API, an old service with a REST endpoint, a warehouse query someone maintains. Atrium takes those the same way it takes a catalogue app: connect it once, decide who may use which parts of it, and it appears alongside everything else.

Whatever the source, the rules are the same. Every call is checked against the person making it and written to the record — a service you wrote on a Friday is governed exactly like the CRM.

A connector we wrote

Available

Hand-built for a specific service, with each tool named and annotated. Pipedrive and Supabase work this way today.

Any REST API

On the roadmap

Point Atrium at an endpoint and describe what it accepts. Your internal services, an old system with an HTTP interface, a partner's API.

An MCP server you already run

On the roadmap

If a team has built one, Atrium passes calls through to it — so it gains permissions and an audit trail without being rewritten.

A catalogue of ready-made apps

On the roadmap

Bulk breadth across the usual SaaS tools, for the long tail nobody wants to hand-build.

In every assistant

4 named, and anything else

One address, pasted once, in whichever assistant you use.

There is no Atrium app to install and no key to configure. You give the assistant an address, it asks you to sign in the first time it needs something, and from then on your systems are simply available to it.

Pick your assistant on the right and copy what it wants. Nothing in these snippets is a secret, so they are safe to paste into a shared config or hand to a colleague.

Run this in your terminal. A browser opens for sign-in the first time you use a tool.

claude mcp add --transport http atrium https://atrium.birdai.ro/api/mcp

Safe by default

nothing shared

Everyone gets their own access, not a shared key.

An assistant can only do what the person driving it is allowed to do. Ask it for something you do not have, and it is refused — before anything is touched, and with the attempt written down. The passwords to your systems never leave Atrium, so no assistant ever holds one.

At the gateway1/4
Agent

bogdan@directimo.comclaude-code

asks fordeal.search{ "term": "atrium" }

read only

Atrium
permission
credential
recorded

Checking who is asking, then what they are allowed.

The recordappend only · chained

allowed refused written down either way

The record is the part most tools skip. Every line is chained to the one before it and sealed, and the database itself refuses to change or delete any of them — so the log holds even against the people who run it. If a line cannot be written, the action does not happen.

One gateway, two people

counted per person

Ana and Bogdan point the same assistant at the same address and get different sets of tools. A system neither can reach is still listed, because “why can’t I see the CRM?” is a question worth answering on the page rather than in a support thread.

ana4/10

works in sales

Pipedrive CRM

Open
4 of 6 tools

Supabase Management API

No access
4 tools · none available
bogdan9/10

runs the platform

Pipedrive CRM

Open
6 of 6 tools

Supabase Management API

Open
3 of 4 tools

Connect it once. Keep the credentials.

Sign in to see what is available to you, or take the address now and point an assistant at it — it will ask you to sign in when it needs to.

Sign in