Cursor MCP servers and Dome
Cursor reaches your tools with each developer signed in as themselves. Put your Gateway in mcp.json and Cursor's first tool call opens a browser. Each developer signs in with their own Dome account. Every sign-in is a grant you can list and revoke, and a refused one is recorded against the person who tried.
Dome provides governed MCP accessfor Cursor.
A URL, no headers
The Gateway goes into mcp.json as a URL alone, with nothing secret in the file.
One repository or all of them
Use .cursor/mcp.json for one project, or ~/.cursor/mcp.json for every project. Both reach the same Gateway and the same rules.
Grants you can see
Every sign-in is a grant, listed in Dome. Revoke a contractor's on their last day and their token stops renewing.
Cursor on a Gatewayin three steps.
Allow your developers, permit the tools, and add one URL to Cursor's mcp.json.
Turn on interactive access
Choose who may sign in from Cursor: exact emails or identity provider subjects. Enabling access gives the Gateway one managed agent.
shelldome gateways interactive enable eng-gateway \ --email lena@example.com \ --email omar@example.comPermit what it may call
Cursor's calls run as that managed agent, so the rule below is applied to it. Find its name with dome gateways get.
shelldome rules apply interactive-access.cedar \ --agent gateway-interactive-<gateway-id> \ --name interactive-accessAdd the Gateway to Cursor
Put it in the project's .cursor/mcp.json, or ~/.cursor/mcp.json for every project. The first tool call opens a browser to sign in.
shellcat > .cursor/mcp.json <<'EOF'{ "mcpServers": { "dome": { "url": "https://<gateway-host>/gateways/<gateway-id>/mcp" } }}EOF
A rulefor the managed agent.
Anyone signed in can see the tools and use GitHub from Cursor, while merging stays with lena.
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 == "lena@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 lena@example.com
github/merge_pull_request(owner: "acme", repo: "app", pullNumber: 905)
- Sign-inlena@example.com is on the allow-list
- TokenInteractive token for eng-gateway, still valid
- RuleMerges are open to lena
DecisionAllowed
Bringing it alltogether.
Connecting Cursor to registered tools and models in Dome completes a governed agent application.
Acting for
Agent
CursorClient
Claude CodeClientControl point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
Models
Common questionsabout Cursor.
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.