> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect an agent

> How an MCP client links to one of your agents.

Anchorage Agentic Banking exposes its tools over MCP. Any MCP-capable client
can connect.

## Prerequisites

* A signed-in Anchorage Agentic Banking account. Sign in with your work SSO,
  or with a one-time code sent to your email.
* 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.

## 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](https://agentic.anchorage.com). Tested clients today:
**Claude Desktop**, **Claude Code**, **Hermes**, **ChatGPT**, **OpenClaw**.
Any other MCP-capable client should work via the standard MCP OAuth flow.

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