Skip to main content
Back to the Mercury MCP server

MCP Gateway · Claude Code

Mercury icon

Connect Mercury to Claude Code

Engineers who build payment or accounting integrations on Mercury need real account data while they debug. Claude Code can read webhook endpoints, transactions and expense categories from the terminal, through the Speakeasy MCP Gateway. Every Mercury tool in the catalog reads data, and each call is logged against the developer who made it.

Category
Sales & CRM
Tools
34
Authentication
OAuth
Claude Code
CLI

Behind the MCP Gateway

Run Mercury MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Mercury call inspected and logged.

Deploy on MCP Gateway

Set up

Add Mercury to Claude Code in 4 steps

  1. 01

    Add Mercury from the catalog

    An admin finds Mercury in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Mercury uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Mercury

    Give teams the mcp:connect scope on the Mercury server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Mercury to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Mercury from Claude Code

    The first time Claude Code connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Mercury needs its own OAuth grant, so each person connects it once. Until they do, Mercury calls fail while the rest of the gateway keeps working.

    From then on, Mercury's tools appear in Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Mercury

Debug a webhook endpoint

When your handler stops receiving Mercury events, Claude Code lists the organization's webhook endpoints, filters by status and shows the one your service registered, so you can compare it with your config.

getWebhooksgetWebhook

Inspect a transaction your code mishandled

Paste a transaction ID from a failing log line and Claude Code pulls the full record, including attachments and related metadata, so you can see which field your parser missed.

getTransactionById

Map expense categories in a sync

Writing a sync to an accounting system? Claude Code lists the organization's custom expense categories and a sample of transactions, so the mapping covers the categories in real use.

listCategorieslistTransactions

Tools

34 tools

Each Mercury tool can be allowed or denied per team and role at the MCP Gateway before Claude Code sees it.

getAccount

Get account by ID

getAccountCards

Retrieve all debit and credit cards associated with a specific account.

getAccountStatements

Retrieve a paginated list of monthly statements for a specific account. Supports cursor-based pagination with limit, order, start_after, and end_before query parameters, as well as date range filtering with start and end parameters.

getTransaction

Get transaction by ID

getAccounts

Retrieve a paginated list of accounts. Supports cursor-based pagination with limit, order, start_after, and end_before query parameters.

getAttachment

Retrieve attachment details including download URL

See all 34 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code exposes to Speakeasy.

Tool logs

Gateway

Every Mercury call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Mercury tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Mercury can reject a tool request before it reaches the server, or withhold a result from Claude Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can Claude Code move money in Mercury?
No. The Mercury tools in this catalog read accounts, cards, transactions, statements, invoices and treasury data. Approval requests for sending money can be listed, but there is no tool to approve or send a payment.
Can engineering get Mercury access without seeing everything finance sees?
Yes. Each of the 34 Mercury tools can be allowed or denied per team and role at the gateway. Engineering could read webhooks and transactions, for example, without access to statements or SAFE requests.
How do Claude Code users get Mercury?
An admin adds Mercury from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Mercury tools their access allows.
Are Mercury calls from Claude Code logged?
Yes. Mercury calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Mercury in other clients

AI everywhere.

Control here.