Admin MCP — set up by chatting

The Admin MCP is the management plane exposed over MCP. Connect Claude (or any MCP client) and do everything the dashboard does — create agents, request spend mandates, issue keys, add tools — with the same permissions and identity checks.

URL: https://api.regentprotocol.org/v1/mcp
Auth: Authorization: Bearer <API key> (from the dashboard → API keys)
Protocol: JSON-RPC 2.0 (initialize, tools/list, tools/call)

On connect the server returns usage instructions (clients like Claude read them as guidance). Call get_started any time to see the flow and where your org stands.

Client config

{
  "mcpServers": {
    "regent-admin": {
      "url": "https://api.regentprotocol.org/v1/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Tools

Start

Tool	What it does	Use case
`get_started`	Explains the flow + your org’s current state	”What do I need to do next?” — the assistant reads it and guides you
`get_kyc_status`	Is the owner identity-verified?	Gate before creating agents/mandates

Agents & mandates

Tool	What it does	Use case
`create_agent`	Register an agent (DID + audit trail)	“Create a shopper-bot agent”
`list_agents` · `get_agent`	Browse / inspect agents	Find an agent’s id + status
`request_mandate`	Request a spend limit — a human approves by email	”Give shopper-bot $10/tx, $50/day” → owner clicks the emailed link
`list_mandates`	See an agent’s mandates	Confirm a limit is active
`get_limit_templates`	Suggested spend-limit presets	Start from a safe “challenge test” limit

⚠️

request_mandate never activates a budget by itself — a human owner must approve the emailed link. An agent can request spend authority but can never grant its own.

Custody wallet

Tool	What it does	Use case
`activate_wallet`	Create a custody wallet (Regent co-signs)	Give an agent its own on-chain account
`get_wallet`	Status, deposit address, balance	Check a wallet is funded before it pays

Cloud Gateway setup

Tool	What it does	Use case
`create_control_key`	Issue the `rgnt_ctrl_…` key the agent presents to the gateway (shown once)	Put it in the agent’s config as the Bearer token
`list_control_keys`	List issued keys (prefixes only)	Audit which agents are connected
`add_gateway_tool`	Add a provider to the catalog	”Add Stripe (form, cents), bound to the mandate”
`list_gateway_tools`	The org’s tool catalog	See what’s available to agents
`list_gateway_credentials`	Which provider keys are vaulted (fingerprints only)	Tell whether a tool is ready to call

The Admin MCP is config + read only — no runtime tool calls, no secret handling. To vault a provider secret, a human does it in the dashboard (/connect/gateway). To use the tools, the agent connects to the Tools MCP.

A full onboarding, in order

get_kyc_status                       → owner verified?
create_agent {name:"shopper"}        → registers the agent
request_mandate {agent, limits}      → owner approves by email
create_control_key {name}            → key shown once → agent config
add_gateway_tool {name, base_url}    → add a provider (e.g. stripe)
   ── then a human vaults the key at /connect/gateway ──
   ── then the agent calls it via the Tools MCP ──

Overview Tools MCP (runtime)