Claude Code, Cursor and Codex for the enterprise
People connect Claude Code, Cursor or Codex to a Gateway and sign in with their own Dome account. Nobody holds a shared key, and every call is audited under the person who made it.
Any MCP client that signs in with OAuthEach person signs in with their own Dome account, audited under their name.
| Integration | Kind | Governed by | Standard |
|---|---|---|---|
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name. | Clients | Tool Gateway | MCP |
Codex on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name. | Clients | Tool Gateway | MCP |
Cursor on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name. | Clients | Tool Gateway | MCP |
Sign-in instead of keys
Turn on interactive access for a Gateway and name who may use it. Each person authorizes once in a browser.
- 1
Turn on interactive access
Dome creates one managed agent for the Gateway. Allow-lists match exact emails or identity provider subjects.
shelldome gateways interactive enable prod-gateway \ --email alice@example.com - 2
Permit what it may call
Write a rule for the managed agent, the same as any agent. Rules can scope by the signed-in person's email.
- 3
Add the Gateway to the client
Give the client the Gateway's MCP URL. The first call opens a browser to sign in.
Commands tested against a Dome workspace on October 1, 2026.
Common questions
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
MCP gateway guide
What an MCP gateway does, and what to ask of one before your people depend on it.