Mercury MCP Server
Connect Mercury to your AI agents with the Mercury MCP server.
Updated
What is Mercury MCP?
The Mercury MCP server is a Model Context Protocol server that connects Mercury to AI agents and assistants as a set of tools. With it connected, an agent can work with Mercury (business banking — accounts, balances, transactions, and payments) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Mercury tools become available to the model.
Connect the Mercury MCP server
Connect Mercury MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Mercury MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Mercury tool to confirm the connection is live.
Connect Mercury MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Mercury
Provide the Mercury MCP server URL or command and complete authentication.
- 3
Test
Reference Mercury from chat to confirm Cursor can reach the tools.
Sample use cases
An agent pulls the latest account balances every morning and posts a cash position summary to a private Slack channel
Leadership sees the daily cash position without logging into the banking portal.
A finance agent monitors incoming transactions and flags any payment above a threshold for review
Large or unexpected transactions are caught immediately.
A scheduled agent reconciles Mercury transactions against invoices in the accounting system and flags mismatches
Monthly close is faster with automated transaction matching.
An agent generates a weekly cash burn report by analyzing outgoing transactions over the past 7 days
Founders and CFOs track runway in real time without manual spreadsheet work.
A compliance agent checks all outgoing transfers against a sanctions watchlist before they are approved
Reduced compliance risk with automated screening on every payment.
An agent categorizes transactions by vendor and department, then updates the budget tracker automatically
Budget tracking stays current without manual data entry.
A scheduled agent exports monthly transaction data and archives it to cloud storage for audit purposes
Clean, timestamped financial records ready for auditors.
Using Mercury MCP with Gamut
On Gamut, the Mercury MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Mercury and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What banking data can the Mercury MCP server access?
The server provides tools to read account balances, transaction history, and account details. Agents can pull real-time financial data for reporting, reconciliation, and monitoring workflows.
Can agents initiate payments through the Mercury MCP server?
The MCP server focuses on read access to financial data. Payment initiation typically requires direct action in Mercury's platform for security reasons, though agents can prepare and queue payment requests for human approval.
Is the Mercury MCP server suitable for startup finance automation?
Yes. Mercury is built for startups and the MCP server is ideal for automating cash monitoring, burn rate tracking, transaction categorization, and investor reporting.
Does the Mercury MCP server support multi-account views?
Yes. Agents can access data across all Mercury accounts (checking, savings, treasury) in a single workflow, enabling consolidated cash position reporting.