Atrium
Get the address

One gateway to everything your company runs on

Sales gets the CRM. Finance gets the ledger. Nobody gets both by accident.

Atrium connects your company’s systems once, then gives each team exactly the ones it should have — inside Claude, Cursor and ChatGPT. Every request is checked against the person making it, and written down.

Sign in

Connect it once

A connector, a REST endpoint, an MCP server you already run. Whatever a team built on a Friday is governed exactly like the CRM.

Everyone gets their own access

An assistant can only do what the person driving it is allowed to do. There is no shared key, and no credential ever leaves Atrium.

Every call is written down

Each line is chained to the one before it and sealed. If a line cannot be written, the action does not happen.

One connection, many doors

6 teams, 19 systems
SwitchboardPick a department
Sales reaches The CRM, Calendars, The shared mailbox, Contracts. The ledger is refused — Finance owns it.
In the tools they already useClaude CodekeyClaude DesktopkeyCursorkeyChatGPTsign inClaude.aisign inAnything elsekeyThe same address in every one of them.

Every department

6 teams

Access is shaped by team, not handed out per person.

Someone joining sales gets what sales gets; someone moving to finance stops getting it the same day.

Sales

chasing deals and keeping the pipeline honest

The CRMCalendarsThe shared mailboxContractsThe ledger

Marketing

running campaigns and reporting on them

AnalyticsThe content libraryAd accountsThe CRM, read onlyHR records

Finance

closing the books and paying everyone

The ledgerInvoicesPayrollSpreadsheetsDatabases

Support

answering customers without keeping them waiting

The ticket queueHelp documentationTeam chatThe CRM, read onlyPayroll

Engineering

shipping, and finding out why something broke

DatabasesCode repositoriesLogsThe ticket queuePayroll

People

hiring, onboarding and everything after

HR recordsPayrollCalendarsPolicy documentsThe ledger

And whatever you built yourself

not just catalogue apps

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 which teams may use which parts, and it appears alongside everything else.

The rules do not change with the source. A service you wrote on a Friday is governed exactly like the CRM.

Connected in this deployment

ANAF — Registrul persoanelor impozabile

2 tools

Romania's tax authority, on the record it publishes: whether a company is registered, for VAT, for split payment and for e-Factura, on a date you name.

Pipedrive CRM

6 tools

The sales pipeline, read and moved: search deals and people, open one deal in full, list activities, and move a deal between stages. Deleting a deal is here too — the one thing in this catalogue that cannot be undone, and the only one that needs approver.

data.gov.ro

3 tools

The Romanian open-data portal. Search what the state has published, and find where a dataset actually lives.

Supabase Management API

4 tools

The account behind your Supabase projects: list them, read table and column definitions, and run SQL. Reading and writing are separate tools on purpose — the read one refuses anything that mutates, and the write one is limited to the scratch schema and needs approver.

A connector we wrote

Available

Hand-built for a specific service, every tool named and annotated. The two above work this way.

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 a record 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

one address

One address, pasted once.

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.

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, with your key in place of the placeholder.

claude mcp add --transport http atrium https://atrium.birdai.ro/api/mcp \
  --header "Authorization: Bearer atrium_YOUR_KEY"

No file to edit — Claude Code writes the config itself. Add --scope project to share it with a repository.

Then say this to it

You're connected to Atrium, my company's gateway. Call atrium_whoami to see what I've got and what's missing, then walk me through setting it up — organisation, team, and whichever applications I should be able to reach.

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 outside your team, 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

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.

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 inGet the address