Mercury

Read Mercury business banking balances, transactions, cards and recipients.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Mercury connector does

The Mercury MCP server connects Mercury business banking to Claude, ChatGPT and any MCP-compatible agent. Mercury documents 31 tools, every one of them a read: balances, transactions, statements, cards, recipients, invoices and treasury. Mercury states the server cannot initiate transactions, and the OAuth token it issues carries a read scope.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Mercury tools (31)

  • load_account
  • load_transaction
  • load_recipient
  • load_account_statement
  • load_accounts_card

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Nothing writes. No tool sends a payment, moves funds between accounts, creates or edits a recipient, issues or freezes a card, or approves anything. If you want an agent to pay a bill, this connector is the wrong tool and Mercury's REST API with an IP-whitelisted Send Money token is the documented path.
  • No approval action exists anywhere in Mercury's public API. Approving or rejecting a queued payment is a web-interface action only, so it is out of reach for any integration, not just this one.
  • The directory's tool list is unusable. Its five load_* names are disjoint from Mercury's 31 and appear in no Mercury documentation.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here and the read/write split is our classification of Mercury's descriptions.
  • It is Beta. Mercury's own warning asks you to double check the model's responses against your Mercury account before any important decision. Do not treat an agent-reported balance as reconciled.
  • Sessions are short in chat clients. About three days on a Claude chat thread, per Mercury. Command line clients last longer because they request offline_access.
  • Recipient bank details are fully exposed to the agent. Account and routing numbers are returned in clear by the recipient tools. Do not connect this server in a shared or public AI session — advice Mercury gives itself.
  • Mercury offers no self-hosted option. Its documentation states plainly that it does not offer a non-hosted MCP at this time, so https://mcp.mercury.com/mcp is the only endpoint.
  • Client names may not begin with "Mercury". Registration fails if they do — a reserved prefix that stops a third-party client presenting itself as Mercury on the consent screen.
  • Rate limits are not published for the MCP server. We found no documented limit, request ceiling or 429 behaviour for https://mcp.mercury.com/mcp, and we did not test it. Treat that as unknown rather than as unlimited.

Frequently asked questions

Can the Mercury MCP server send a payment or move money?

No. Mercury states its hosted MCP is limited to read-only actions and cannot initiate transactions or modify account data. All 31 documented tools are get or list operations. Mercury's payment endpoints, createTransaction and requestSendMoney, exist in the REST API but are absent from the MCP tool list, and the OAuth token is issued with a read scope.

Can the connector approve a payment that is waiting for approval?

No, and nothing in Mercury's public API can. The MCP tool listSendMoneyApprovalRequests only reads the queue of pending payments. Mercury publishes no approve or reject endpoint anywhere in its API reference, so approval happens exclusively in the Mercury web interface by a human with send-money permission. The connector can see a pending payment but not act on it.

Why does Anthropic's directory list 5 Mercury tools when the docs list 31?

The two lists are entirely disjoint and one of them is stale. Anthropic's snapshot from 2026-01-12 shows five snake_case names such as load_account, none of which appears anywhere in Mercury's documentation. Mercury's own tool page, updated 2026-07-27, lists 31 camelCase names. Treat the vendor list as current and the directory as an old naming scheme.

What OAuth scopes does the Mercury MCP server request?

Two, and both are narrow. Mercury's RFC 9728 resource descriptor declared scopes_supported of read and offline_access on 2026-08-22. The read scope is the entire data grant, and offline_access only lets a client refresh its token without sending you back to the browser. There is no write scope to grant, which is why the boundary holds.

What sensitive data can the Mercury connector read?

Full bank routing and account numbers for your payment recipients, plus balances, complete transaction history with counterparties, statements and your EIN. Mercury's own security guidance names recipient routing numbers and account information explicitly. Card tools return only the last four digits. Read-only does not mean low risk here — the read surface is the whole risk.

Do I need to set anything up in Mercury before connecting?

No. Mercury states there is nothing to set up on its side and that your AI tool registers itself the first time it connects, using OAuth 2.0 Dynamic Client Registration. Adding the server grants no access on its own; Mercury issues a token only after you sign in and select Allow at its own consent screen.

Why does my Mercury connection stop working after a few days?

The session expired and needs a fresh sign-in. Mercury states a Claude connector session lasts about three days on the same chat thread. Command line tools last longer because Mercury returns a refresh token to any client that requests the offline_access scope. Run claude mcp login mercury to sign in again.

Is the Mercury MCP server production-ready?

Mercury labels it Beta. Its documentation carries a warning that the MCP is in Beta while the team understands the limitations of chat models, and asks you to double check any response from the model against your Mercury account before making important decisions. Treat figures the agent reports as a draft, not as a reconciled statement.

Sources

More Finance connectors

  • Affinity

    Search your CRM, prep for meetings and update deal records from your AI assistant.

  • Aiera

    Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.

  • Airwallex Developer

    Search Airwallex documentation and exercise a sandbox account from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Mercury to work.

Connect Mercury once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.