Skip to main content
Back to the Mercury MCP server

MCP Gateway · Codex

Mercury icon

Connect Mercury to Codex

Finance automation usually lives in scripts and scheduled jobs that someone has to verify. Codex can check those jobs against live Mercury data: whether an import caught every transaction, what a statement looks like, and which legal entity details a config should carry. Agent hooks send each prompt and Mercury tool call to Speakeasy before Codex runs it.

Category
Sales & CRM
Tools
34
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

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 Codex 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 Codex

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Mercury from Codex

    The first time Codex 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 Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Mercury

Verify a transaction import job

After a nightly import runs, ask Codex to list Mercury transactions for the same date range across all accounts and compare the count with what your database stored.

getAccountslistTransactions

Script statement downloads

Codex reads the monthly statements for an operating account and a treasury account, then writes a script that pages through them with the cursor parameters the API expects.

getAccountStatementsgetTreasuryStatements

Fill entity details in a config

When a vendor integration asks for the company's legal name, EIN or DBAs, Codex reads them from Mercury instead of copying them from an old email.

getOrganization

Tools

34 tools

Each Mercury tool can be allowed or denied per team and role at the MCP Gateway before Codex 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 Codex

The gateway covers every client the same way. The rest depends on what Codex 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 Codex. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Codex

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

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Who can roll out Mercury in Codex for a team?
A ChatGPT workspace admin on a Business, Enterprise or Edu plan imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
Is Mercury data redacted before it reaches Codex?
PII redaction and prompt injection detection run on every Mercury tool call at the gateway. Each call is also logged against a named employee and can be exported to your SIEM.
How do Codex users get Mercury?
An admin adds Mercury from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Mercury tools their access allows.
Are Mercury calls from Codex 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.