Skyvern MCP server and Dome

1. 01

   Add the Skyvern MCP server

   Each person connects their own Skyvern account on their first call. Dome holds the token.

   $ dome tools add --name skyvern \
     --url https://api.skyvern.com/mcp/ \
     --auth-method oauth --credential-type per-user \
     --oauth-authorize-url https://api.skyvern.com/oauth/authorize \
     --oauth-token-url https://api.skyvern.com/oauth/token \
     --oauth-registration-url https://clerk.skyvern.com/oauth/register \
     --gateway ops-gateway

2. 02

   Sync the catalog

   Sync spends your own Skyvern credential, so sign in first. Until then it fails and agents get “tool not available in this gateway”.

   $ dome tools catalog sync skyvern

3. 03

   Apply the rules

   Scope them to one agent while you try them. Simulate before you deploy.

   $ dome rules apply skyvern-permit.cedar skyvern-portals.cedar \
     --agent claims-filer --name skyvern-portals

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

permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)
when {
  resource.connection_name == "skyvern" &&
  ["skyvern_browser_session_create", "skyvern_browser_session_close", "skyvern_navigate",
   "skyvern_login", "skyvern_act", "skyvern_extract"].contains(resource.tool_name)
};
 
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)
when {
  resource.connection_name == "skyvern" &&
  ["skyvern_navigate", "skyvern_login"].contains(resource.tool_name) &&
  !(resource has arguments &&
    resource.arguments has url &&
    (resource.arguments.url like "https://portal.coastal-mutual.com/*" ||
     resource.arguments.url like "https://claims.brightline-health.com/*"))
};