Announcing Dome Managed Agents.

Try it now

Harvey MCP and Dome

Harvey reaches your firm's systems with each lawyer signed in as themselves. Harvey connects to a firm's own MCP server over OAuth, and each user signs in for their own account. Point it at a Dome Gateway, and every lawyer signs in with their Dome account. Rules decide each call by person, and audit records every one under their name.

Dome provides a governed gatewayfor Harvey.

Each lawyer signs in

Harvey sends every user through sign-in on their first connection. With Dome, that sign-in is the lawyer's own Dome account.

Rules per lawyer

Rules read the signed-in lawyer's email. Associates search the know-how base, and partners can add to it.

Audit by name

Every call Harvey makes is recorded under the lawyer who made it. Revoke one person's grant and leave the rest.

Harvey on a Gatewayin three steps.

Turn on interactive access, permit what it may call, and add the Gateway to Harvey as your own MCP server. Each lawyer authorizes once in a browser.
  1. Turn on interactive access

    Name who may sign in, by exact email or identity provider subject. Dome creates one managed agent for the Gateway.

    shell
    dome gateways interactive enable firm-gateway \  --email partner@example.com \  --email associate@example.com
  2. Permit what it may call

    Apply the rule below to the managed agent. Its name is in dome gateways get.

    shell
    dome rules apply harvey-notion.cedar \  --agent gateway-interactive-<gateway-id> \  --name harvey-notion
  3. Add the Gateway to Harvey

    A Harvey workspace admin adds the Gateway's MCP URL as the firm's own server and enables it. Each lawyer then signs in once from Harvey.

Search for everyone,write for partners.

Everyone signed in may discover tools, search and fetch pages. Only the partner may have Harvey create a page.
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 == "notion" &&  ["notion-search", "notion-fetch", "notion-create-pages"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "notion" &&  resource.tool_name == "notion-create-pages"}unless {  principal has act_as &&  principal.act_as.email == "partner@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-4be2 · acting as partner@example.com
notion/notion-create-pages(parent: "Precedents", title: "Indemnity cap, SaaS MSA")
  1. Sign-inpartner@example.com is on the allow-list
  2. TokenInteractive token for firm-gateway, still valid
  3. RuleNew pages are open to the partner
DecisionAllowed

Bringing it alltogether.

Connecting Harvey to registered tools, identity, and models in Dome completes a governed agent application.
Dome

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Tools

HarveyAgent service
NotionMCP server

Common questionsabout Harvey.

Can Harvey connect to our own MCP server?
Yes. Harvey's Bring Your Own MCP connects a firm's server over HTTPS with OAuth, and a Dome Gateway with interactive access is that server.
Does each lawyer need a Dome account?
Yes. Each person signs in with their own Dome account, which needs access to the workspace as well as a place on the allow-list.
Can different lawyers get different access through Harvey?
Yes. Rules read the signed-in person's email, so one Gateway can give partners and associates different tools.
How do I remove one person's access?
Revoke their interactive grant in Dome, or take them off the allow-list, and everyone else keeps working.

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

LangGraph

LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client

Codex

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