Announcing Dome Managed Agents.

Try it now

GitHub MCP server and Dome

Let agents open pull requests, and decide where they can merge. Connect the GitHub MCP server to Dome once. Every call runs with the GitHub token of the person the agent acts for, and rules decide each call on its repository.

Dome provides a tool gatewayand authorization for GitHub.

Decided on the arguments

One tool, allowed on one repository and refused on another. Rules read the owner and repo of every call.

Their token, their permissions

Attach a GitHub token for each engineer. An agent acting for one reaches only what they can.

Outside repositories refused

Calls to an owner other than your organization are refused. A prompt can't point an agent at someone else's fork.

GitHub behind the Gatewayin three steps.

Add the server, sync its tools into the Gateway's catalog, and apply the rules. Agents reach GitHub through the Gateway's single MCP endpoint.
  1. Add the GitHub MCP server

    Credentials are per user. Dome holds each engineer's GitHub token and injects it on calls made for them.

    shell
    dome tools add --name github \  --url https://api.githubcopilot.com/mcp/ \  --auth-method api-key \  --credential-type per-user \  --gateway eng-gateway
  2. Sync the catalog

    Run it once a token is attached, and again when GitHub adds tools. Until then, agents get “tool not available in this gateway”.

    shell
    dome tools catalog sync github
  3. Apply the rules

    Scope them to one agent while you try them, and simulate before you deploy.

    shell
    dome rules apply github-permit.cedar github-args.cedar \  --agent release-drafter --name github-per-argument

Merge anywherebut payments.

The permit opens GitHub to the agent. The first forbid refuses merges into acme/payments, and the second refuses any owner outside acme.
cedar
permit (principal, 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" &&  resource has arguments &&  resource.arguments has owner && resource.arguments has repo &&  resource.arguments.owner == "acme" && resource.arguments.repo == "payments"};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "github" &&  resource has arguments &&  resource.arguments has owner && resource.arguments.owner != "acme"};

One call,two outcomes.

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

Repository

agent dependency-bot · acting as d.osei
github/merge_pull_request(owner: "acme", repo: "web", pullNumber: 482)
  1. Agentdependency-bot is registered and active
  2. Callerd.osei verified through Okta
  3. RuleGitHub calls inside acme are allowed
DecisionAllowed

Three agentson GitHub.

These come from our template library, and each one reads broadly and writes narrowly.

pr-reviewer

Review pull requests

Reads the diff and the files around it and leaves a first review, while approval stays with an engineer.

release-drafter

Draft release notes

Reads the pull requests merged since the last release and drafts customer-facing notes.

dependency-bot

Merge dependency updates

Reviews dependency update pull requests and merges the ones that pass their checks, while protected repositories stay with an engineer.

Bringing it alltogether.

Connecting GitHub to registered agents, models, and identity in Dome completes a governed agent application.
Dome

Acting for

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Tools

GitHubMCP server

Common questionsabout GitHub.

Does Dome work with GitHub's remote MCP server?
Yes. Add it by URL, attach a token per user, and sync its tools into the Gateway's catalog.
Can I allow a GitHub tool on some repositories and not others?
Yes. Rules read the arguments of every tool call, so the same tool can be allowed on one owner and repository and refused on another.
Whose GitHub permissions does an agent use?
With per-user credentials, the permissions of the person it acts for. Dome picks their token from their verified identity.
Why write rules against connection_name and not the tool's full name?
Dome rewrites connection names to ids when rules deploy. A pattern on the full tool name isn't rewritten, so a forbid written that way deploys and matches nothing.

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.
Identity

Microsoft Entra ID

Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
Runtime

OpenAI Agents SDK

OpenAI Agents SDK agents with their models on the Model Broker and their MCP tools on the Tool Gateway.
Client

Claude Code

Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
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.

MCP servers for AI agents: per-argument rules on every call

Put any remote MCP server behind the Tool Gateway. Agents reach it through one governed endpoint, and rules decide each call on its arguments.

Every agent you run, under one system of control.