Announcing Dome Managed Agents.

Try it now

Skyvern MCP server and Dome

Let agents work your portals, and decide which ones. Skyvern drives a browser through forms and logins from plain-language instructions. Connect its hosted MCP server to Dome once, and rules decide every navigation and login on its URL. Each person's Skyvern account stays in Dome, and every step lands in one audit trail.

Dome provides a governed gatewayfor Skyvern.

Logins decided on the URL

Rules read the URL of every navigation and login. A payer portal on the list opens, and a lookalike domain is refused.

Passwords never reach the agent

skyvern_login signs in with a credential stored in Skyvern. Dome holds each person's Skyvern token, so the agent sees neither.

Every step on the record

Navigations, logins, actions and extractions are each a tool call. The audit trail shows which person each one ran for.

Skyvern behind the Gatewayin three steps.

Add the hosted MCP server with OAuth, sync its tools into the Gateway's catalog, and apply the rules. Dome registers its own OAuth client with Skyvern.
  1. Add the Skyvern MCP server

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

    shell
    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. 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”.

    shell
    dome tools catalog sync skyvern
  3. Apply the rules

    Scope them to one agent while you try them, and simulate before you deploy.

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

Log in to two portals,nothing else.

The permit opens the browser tools to the agent. The forbid refuses any navigation or login whose URL isn't on one of two payer portals, and a login with no URL is refused too.
cedar
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/*"))};

One call,two outcomes.

Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.

Site

agent claims-filer · acting as d.mensah
skyvern/skyvern_login(credential_type: "skyvern", credential_id: "cred_coastal", url: "https://portal.coastal-mutual.com/login")
  1. Agentclaims-filer is registered and active
  2. Callerd.mensah verified through Microsoft Entra ID
  3. Ruleportal.coastal-mutual.com is on the list
DecisionAllowed

Three agentson Skyvern.

Each one works a short list of portals, for the specialist it acts for. A bundle per agent keeps the lists apart.

claims-filer

File claims on payer portals

Logs in to two payer portals and fills each claim form from the case file, and is refused on any other site.

eligibility-checker

Check member eligibility

Looks up coverage for each new case and extracts the plan details, reading without ever submitting.

remittance-collector

Collect remittance notices

Signs in to each payer weekly and extracts new remittance totals for finance.

Bringing it alltogether.

Connecting Skyvern to registered agents, models, and identity in Dome completes a governed agent application.
Dome

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Tools

SkyvernAgent service

Models

Common questionsabout Skyvern.

Does Skyvern have a hosted MCP server?
Yes. Skyvern hosts one at api.skyvern.com/mcp/ with OAuth, and Dome adds it by URL and registers its own client.
Can I limit which portals a Skyvern agent logs in to?
Yes. Rules read the URL argument of skyvern_navigate and skyvern_login, so a listed portal opens and any other host is refused.
Does the agent ever see the portal password?
No. skyvern_login signs in with a credential stored in Skyvern, and Dome holds the Skyvern token for each person.
Whose Skyvern account does an agent use?
The account of the person it acts for. Dome holds a token for each person and picks it from their verified identity.

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

GitHub

The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Identity

Okta

Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime

OpenAI Agents SDK

OpenAI Agents SDK agents with their models on the Model Broker and their MCP tools on the Tool Gateway.
Client

Claude Code

Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.

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.

Agent services: web, research, payments, voice and sandboxes

Web actions, research, payments, phone calls and code execution are where agents reach past your walls. Put each service behind the Gateway, and every call is authorized, metered and audited.

Every agent you run, under one system of control.