Skip to main content
The Dome MCP server exposes platform tools organized into groups. Tools are filtered based on your workspace, tenant, and org roles — you only see tools matching your permissions.

​
Setup

​
Claude Integration

Register the Dome MCP server with Claude Code:
Claude discovers available tools automatically. Switch workspaces mid-session with dome_context_use — the tool list updates to reflect your new permissions.

​
Guided prompts

The MCP server ships three guided prompts that run end-to-end onboarding flows from your client. Invoke them with /dome:quickstart, /dome:tutorial, or /dome:adopt in Claude Code (other clients expose prompts through their own UI).

Quickstart

Role-aware first-time setup.

Tutorial

Guided governed-agent walkthrough.

Adopt

Brownfield onboarding — route an existing codebase’s LLM traffic through the gateway with no code changes.

​
Tool Groups

Context Management

9 tools — switch workspaces, manage aliases, check auth status. Always available.

Agent Registry

13 tools — register agents, manage lifecycle, create and rotate API keys.

Authorization Rules

10 tools — deploy Cedar rules, simulate decisions, rollback bundles.

Audit

4 tools — query, inspect, and export audit events, and report LLM token usage and cost.

Webhooks

14 tools — manage event subscriptions, inspect and replay deliveries, browse the provider catalog.

Platform Management

7 tools — platform status, API keys (list, create, revoke, available permissions), configuration, tenant creation.

Workspaces

11 tools — create workspaces, manage members, configure act-as enforcement and policy freshness, provision sandboxes.

Tools

MCP server connection CRUD, catalog discovery, and shared-OAuth connect/disconnect.

Gateways

24 tools — create Gateways, curate membership, grant agent access, set cost caps.

LLM Models

LLM model connections and routing pools across Anthropic, OpenAI, Azure, Google, and Bedrock.

Verification Providers

3 tools — manage OIDC and HMAC verification providers.

​
Permission Model

After selecting a context with dome_context_use, tools are filtered based on your workspace, tenant, and org roles. Higher-scope roles cascade into the tools visible inside a workspace context (an org owner sees every workspace tool). A handful of tools are gated only by an active context (no role requirement) — refer to Context and the platform tools dome_status_get, dome_config_get, dome_workspaces_list, dome_workspaces_get, dome_platform_keys_available_permissions. Tenant-level tools like dome_workspaces_create and dome_provision_sandbox require a tenant role; the tenant management tools dome_tenants_list, dome_tenants_get, and dome_tenants_create require an org role.
Context management tools are always available regardless of role. You do not need workspace context to list or switch contexts.

​
Tool Documentation Standard

Each MCP tool page documents:
  • Tool name — the exact dome_* identifier used in JSON-RPC calls
  • Parameters — typed parameter table with required/optional markers
  • Description — one-line purpose
  • Permission — which RBAC role(s) can access the tool
  • Destructive flag — whether the tool modifies or deletes data
Tools follow the MCP specification for tool discovery and invocation. The server returns tool schemas via tools/list that MCP clients use for auto-discovery.

​
Next steps

Connect a client, then start with Agents or Rules:
  • Setup AI assistant to connect Claude or another client
  • Agents for the first tool group most operators use
  • Rules to draft and deploy Cedar from an assistant
  • Quickstart to verify governed traffic end to end