Independent review. Unpaid; no partnership with Mercury. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Business banking for startups. Mercury MCP (in beta) connects AI tools over OAuth to read accounts and transactions and to request payments or transfers, which still need approval in Mercury; an API is also documented.
The Ion perspective
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
Value
Business banking for startups. Mercury MCP (in beta) connects AI tools over OAuth to read accounts and transactions and to request payments or transfers, which still need approval in Mercury; an API is also documented.
Differentiation
Documented fit: Startups wanting banking data in their own dashboards. Uniqueness is not established.
Replaceability and switching
Compare Ramp. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Businesses that need branch banking. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
IonBin provides general information and software comparisons, not tax, legal, accounting or financial advice. Tax and legal rules vary by situation and jurisdiction; consult a qualified professional (CPA, enrolled agent or attorney) before acting.
AI tools can make mistakes. Verify every figure against the original documents and official IRS or state guidance before filing or signing.
Redact Social Security numbers, account numbers and EINs before uploading documents to any AI assistant, and check its data-retention settings. Upload originals only to the filing or signing software.
Best for
Startups wanting banking data in their own dashboards
Not for
Businesses that need branch banking
Top use cases
Read balances and transactions through the API source ↗
Ask about balances and transactions, and request payments that still need approval in Mercury source ↗
In depth
Plans
Mercury lists base banking at $0/month, with optional plans and fees for certain features or transactions. Its annual-pricing view shows Plus $29.90 and Pro $299 per month; the FAQ gives paid plans from $35/month. Confirm the annual total at checkout. Treasury requires an eligible $250,000 Mercury balance. Mercury is a fintech company; banking services come from partner banks. source ↗
MCP (beta)
MCP is beta. It can request payments to existing recipients and transfers between your Mercury accounts, but approval must happen in Mercury—even when normal policies would otherwise waive approval. Category and note edits apply immediately with permission. Existing read-only connections need reauthorization for writes. Check request status before retrying an uncertain result. source ↗
How to use it with AI
How Mercury connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
Not documentedVerify which side exports and which imports, supported formats and permissions. Mercury's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route.Mercury file docs ↗Claude (incl. Claude Code) file docs ↗
Not documentedOpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Mercury publishes an API, but this pairing still needs network, authentication and execution-scope checks.Mercury API ↗OpenAI Codex docs ↗
InferredOnly in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Mercury is a web app; the pairing itself is not documented.OpenAI Codex browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Mercury's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route.Mercury file docs ↗OpenAI Codex file docs ↗
InferredThe /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Mercury is a web app; the pairing itself is not documented.Google Antigravity browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Mercury's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route.Mercury file docs ↗Google Antigravity file docs ↗
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Corporate cards, expenses and bill pay with spend controls. Its MCP server lets assistants query spend and act on supported approvals, reimbursements and cards within user permissions. A separate developer API is documented.