Skip to main content
Anchorage Agentic Banking exposes its tools over MCP. Any MCP-capable client can connect. For programmatic discovery, see Discovery.

​
Prerequisites

  • A signed-in Anchorage Agentic Banking account. Sign in with your work SSO, or with a one-time code sent to your email. Repeated code attempts for one email address are limited; if a correct code is rejected, wait a moment and try again.
  • At least one agent created on the Agents page in the web UI, with a budget assigned by your org admin.

​
How linking works

When an MCP client connects to Anchorage Agentic Banking, it triggers an OAuth consent flow in your browser. During that flow, you pick which of your agents this MCP session is linking to. The chosen agent’s identity is what the client will act under — every tool call from that session is attributed to that agent, and every spend draws on that agent’s budget. If you have not picked an organization yet — on your first sign-in, or when you belong to several — the flow sends you to the organization picker first, where you pick one, accept an invitation, or join an organization open to your email domain. Picking one returns you to the consent screen, so you finish linking without restarting from the client. Two cases do need a restart from the client: taking more than thirty minutes to pick, or a client authorize request too long for the browser to remember, both of which land you on the dashboard after you pick. Registering a client and revoking a token carry request limits — see Request limits.

​
Per-client setup

Per-client configuration snippets, the MCP endpoint URL, and the OAuth consent itself all live on the Agents page at agentic.anchorage.com. Tested clients today: Claude Code, Hermes, OpenClaw, and Replit, each with its own tab. Any other MCP-capable client should work through the standard MCP OAuth flow; point it at the endpoint URL on the Other tab. Needs a paid ChatGPT plan, on chatgpt.com. To add Anchorage Agentic Banking to ChatGPT as a custom MCP server, follow the ChatGPT tab.

​
Harnesses on a machine with no browser

A harness like OpenClaw or Hermes running on a server with no browser connects with an agent API key, or with OAuth consent completed on another device where the harness supports it. See Connect your harness.

​
First call

The agent’s first turn should introspect its own identity. The response includes the agent’s name, status, linked account, network scope, and its budgets — enough to start paying without a second round trip.