Cursor MCP servers and Dome

1. 01

   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.

   $ dome gateways interactive enable eng-gateway \
     --email lena@example.com \
     --email omar@example.com

2. 02

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

   $ dome rules apply interactive-access.cedar \
     --agent gateway-interactive-<gateway-id> \
     --name interactive-access

3. 03

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

   $ cat > .cursor/mcp.json <<'EOF'
   $ {
     "mcpServers": {
       "dome": {
         "url": "https://<gateway-host>/gateways/<gateway-id>/mcp"
       }
     }
   $ }
   $ EOF

Commands and rules tested against a Dome workspace on October 1, 2026. For anything about Cursor itself, see Anysphere's documentation.

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"
};