Announcing Dome Managed Agents.

Try it now

MCP servers for AI agents

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

Any remote MCP serverAdd it by URL, and rules decide each call on its arguments.

Integration catalog
IntegrationKindGoverned byStandard
The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
MCP serversTool GatewayMCP
The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
MCP serversTool GatewayMCP
HubSpot's remote MCP server behind the Tool Gateway, with CRM updates allowed and publishing and schema changes refused.
MCP serversTool GatewayMCP
Linear's MCP server behind the Tool Gateway, with rules that decide each issue write on its team.
MCP serversTool GatewayMCP
Notion's hosted MCP server behind the Tool Gateway, with rules that decide each edit on its page and command.
MCP serversTool GatewayMCP
Salesforce's hosted MCP server behind the Tool Gateway, with rules that decide each write on the object it names.
MCP serversTool GatewayMCP
Sentry's remote MCP server behind the Tool Gateway, with rules that decide triage calls on their arguments.
MCP serversTool GatewayMCP
Slack's MCP server behind the Tool Gateway, with rules that decide each message on its channel.
MCP serversTool GatewayMCP
Snowflake's managed MCP server behind the Tool Gateway, with rules that decide each search on its columns and size.
MCP serversTool GatewayMCP
The Stripe MCP server behind the Tool Gateway, with live mode read-only and writes confined to a sandbox.
MCP serversTool GatewayMCP
1–10 of 10

Any remote MCP server in three steps

Add the server by URL, sync its tools into the Gateway's catalog, and apply rules, using GitHub as the example here.
  1. 1

    Add the server

    Its credential stays in Dome, shared or per user.

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

    Sync the catalog

    Agents get “tool not available in this gateway” until the catalog is synced.

    shell
    dome tools catalog sync github
  3. 3

    Decide on arguments

    Rules read the tool's name and its arguments.

    cedar
    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 repo &&  resource.arguments.repo == "payments"};

Commands tested against a Dome workspace on September 30, 2026.

Common questions

Which MCP servers work with Dome?
Any remote MCP server. Add it by URL, attach its credential, and sync its tools.
Can a rule look at a tool call's arguments?
Yes. The same tool can be allowed with one argument and refused with another.
Do agents need a credential for each server?
No. Each agent holds one Dome key. Dome holds each server's credential and injects it on the call.

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 agents depend on it.

Every agent you run, under one system of control.