Mercury
Give the Sazabi agent tools to search banking context such as accounts, cards, recipients, transactions, treasury records, and organization data in Mercury.
About
Mercury is an MCP connector that gives the Sazabi agent tools to search banking context such as accounts, cards, recipients, transactions, treasury records, and organization data. Mercury's hosted MCP server authenticates via OAuth with dynamic client registration. Once connected, agents can read Mercury data through the hosted MCP endpoint. The Mercury hosted MCP service is read-only.
What the agent can do:
- Search and review Mercury accounts and account metadata
- Browse transactions, recipients, counterparties, and status details
- Retrieve card, cardholder, treasury, and organization records
- Add banking context to investigations without changing Mercury data
Prerequisites
- An active Mercury account with access to the desired organization
- Permission to authorize third-party OAuth applications in Mercury
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Mercury in Settings > MCP connectors.
Authorize
Start the connection; Sazabi redirects you to Mercury to authorize, then back.
Set up with the CLI
You can also connect Mercury with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
Mercury authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect mercuryAdd --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized (OAuth) or the key/header is correct (token auth).
Troubleshooting
No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.
Connection shows needs attention — The authorization or key may have expired or been revoked; reconnect from Settings > MCP connectors.