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 | Kind | Governed by | Standard |
|---|---|---|---|
The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site. | MCP servers | Tool Gateway | MCP |
The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository. | MCP servers | Tool Gateway | MCP |
HubSpot's remote MCP server behind the Tool Gateway, with CRM updates allowed and publishing and schema changes refused. | MCP servers | Tool Gateway | MCP |
Linear's MCP server behind the Tool Gateway, with rules that decide each issue write on its team. | MCP servers | Tool Gateway | MCP |
Notion's hosted MCP server behind the Tool Gateway, with rules that decide each edit on its page and command. | MCP servers | Tool Gateway | MCP |
Salesforce's hosted MCP server behind the Tool Gateway, with rules that decide each write on the object it names. | MCP servers | Tool Gateway | MCP |
Sentry's remote MCP server behind the Tool Gateway, with rules that decide triage calls on their arguments. | MCP servers | Tool Gateway | MCP |
Slack's MCP server behind the Tool Gateway, with rules that decide each message on its channel. | MCP servers | Tool Gateway | MCP |
Snowflake's managed MCP server behind the Tool Gateway, with rules that decide each search on its columns and size. | MCP servers | Tool Gateway | MCP |
The Stripe MCP server behind the Tool Gateway, with live mode read-only and writes confined to a sandbox. | MCP servers | Tool Gateway | MCP |
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
Add the server
Its credential stays in Dome, shared or per user.
shelldome 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
Agents get “tool not available in this gateway” until the catalog is synced.
shelldome tools catalog sync github - 3
Decide on arguments
Rules read the tool's name and its arguments.
cedarforbid (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
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.