Announcing Dome Managed Agents.

Try it now

Claude Code MCP and Dome

Every developer signs in, and every tool call is checked. Commit one .mcp.json and every developer who clones the repository gets your Gateway. Each signs in with their own Dome account the first time they run /mcp, and rules decide what Claude Code may call for them.

Dome provides governed MCP accessfor Claude Code.

The config ships with the repository

Project scope writes the Gateway URL to .mcp.json and nothing else. Commit it, and a new hire's first /mcp opens the sign-in.

Same repository, different reach

Rules read who signed in. Everyone on the repository can have Claude Code open pull requests, but only alice can have it merge one.

One merge, one name

Audit records each tool call under the developer who signed in. A merge Claude Code made is a merge alice made.

Claude Code on a Gatewayin three steps.

Allow your developers, permit the tools, and commit the Gateway to the repository's .mcp.json.
  1. Turn on interactive access

    List the developers who may sign in from Claude Code, by exact email or identity provider subject. Dome creates the Gateway's managed agent.

    shell
    dome gateways interactive enable eng-gateway \  --email alice@example.com \  --email bob@example.com
  2. Permit what it may call

    The rule below goes on that managed agent. dome gateways get shows its name.

    shell
    dome rules apply interactive-access.cedar \  --agent gateway-interactive-<gateway-id> \  --name interactive-access
  3. Add the Gateway to Claude Code

    Project scope writes .mcp.json, which holds no secret and can be committed. Run /mcp in Claude Code to sign in.

    shell
    claude mcp add --transport http --scope project dome \  https://<gateway-host>/gateways/<gateway-id>/mcp

A rulefor the managed agent.

Every signed-in developer may list tools and call GitHub. The merge tool is refused unless alice is the one signed in.
cedar
permit (  principal is Dome::Agent,  action == Dome::Action::"mcp:discover",  resource);
permit (  principal is Dome::Agent,  action == Dome::Action::"mcp:call",  resource is Dome::MCPTool) when { resource.connection_name == "github" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "github" &&  resource.tool_name == "merge_pull_request"}unless {  principal has act_as &&  principal.act_as.email == "alice@example.com"};

One call,two outcomes.

Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.

Signed in as

agent gateway-interactive-1d85 · acting as alice@example.com
github/merge_pull_request(owner: "acme", repo: "web", pullNumber: 482)
  1. Sign-inalice@example.com is on the allow-list
  2. TokenInteractive token for eng-gateway, still valid
  3. RuleMerges are open to alice
DecisionAllowed

Bringing it alltogether.

Connecting Claude Code to registered tools and models in Dome completes a governed agent application.
Dome

Agent

Claude CodeClient
CursorClient

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Common questionsabout Claude Code.

How do I secure Claude Code's MCP servers?
Put them behind a Dome Gateway and add the Gateway to Claude Code. Each developer signs in, and rules decide every tool call.
Does each developer need an API key?
No. /mcp opens a browser to sign in. Claude Code keeps a token that lasts at most 10 minutes and renews while the developer is still allowed.
Can my team share the Claude Code MCP config?
Yes. Add the Gateway with --scope project and commit .mcp.json, since it holds only the URL.
Can I allow a whole group to sign in?
No. Allow-lists match exact emails or identity provider subjects.

More of whatDome works with.

Model

Claude Fable

Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider

Anthropic

The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server

Atlassian

The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
Identity

Okta

Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime

LangGraph

LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Agent service

TinyFish

TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.

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.

Claude Code, Cursor and Codex: governed MCP access for your people

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.

Every agent you run, under one system of control.