Banking
Mercury MCP connector
The Mercury connector brings your business bank accounts, transactions, cards, customers, invoices and payment recipients into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person on your team can ask questions and get work done inside their own Mercury access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Mercury to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Mercury once
-
Open Connections, choose Add connection, and pick Mercury.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Mercury API key. One person generates a token in Mercury and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Mercury to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Mercury to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Mercury to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Mercury to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Mercury through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Find a transaction without opening Mercury
Ask which payments went out last week, who they went to and what they were for, and get the answer from live Mercury transactions across every account.
-
Accounting
Add a memo to a transaction after month end
Catch a Mercury transaction up with the note or category it was missing so the books close without a hunt through the statement.
-
Billing
Draft and send a customer invoice
Create a Mercury customer for a new client, then raise the invoice for the agreed amount and check later whether it is still outstanding.
-
Operations
Set up a new vendor as a recipient
Add a supplier as a Mercury recipient with their payment details, then arrange a payment to them from the right account once approved.
-
Founders
Check the balance across every account
Ask for a quick view of all Mercury accounts before a big decision, and see which account is best placed to cover it.
-
Operations
Issue a card for a new hire
Create a Mercury card for someone joining, adjust it when their role changes, and remove it when they no longer need it.
Try asking
- “List last week's Mercury transactions over 5,000 dollars.”
- “Which Mercury cards were issued this month, and to whom?”
- “Show balances across all Mercury accounts today.”
AI tools
Mercury tools for your AI agents
70 tools are ready to call through Elaichi's MCP endpoint the moment you connect Mercury, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Mercury gets you
6 screens from the product, each doing one job for your Mercury account.
The agent
Ask about accounts, get answers from Mercury.
Plain language questions return live Mercury transactions, cards and customer records.
- accounts
- transactions
- cards
- customers
Ask Elaichi to work across your apps.
List last week's Mercury transactions over 5,000 dollars.
Which Mercury cards were issued this month, and to whom?
Show balances across all Mercury accounts today.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Mercury together.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
70 Mercury tools are ready to call.
Accounts, transactions, cards and customers are covered with no custom code.
- List all Mercury account
- List all Mercury transaction
- Get single Mercury transaction by ID
- Create a Mercury transaction
Toolboxes
Every team gets its own Mercury toolbox.
Curate one toolbox for finance and another for treasury, scoped per team.
- Finance
- Accounts payable
- Treasury
- Operations
Shared connections
Teammates use Mercury without seeing a credential.
See who connected each Mercury account and how many teams and members share it.
- Operating account
- Payroll
- Treasury reserve
- Corporate cards
Audit log
Every Mercury call is on the record.
When, who, what happened, type and resource, appended for each transaction and card.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and Mercury work finishes.
Fetch transactions, group them, draft a digest, approve it, post back to Mercury.
Mercury digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch accounts
Mercury
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Mercury
Queued
Collections and dashboards
Mercury numbers land before anyone asks.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Mercury health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Transactions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Operating account 34%
Payroll 27%
Treasury reserve 21%
Corporate cards 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Mercury to Claude?
In Elaichi, choose Mercury and paste in an API key from your Mercury account, which takes about a minute. There is no client ID or secret to generate and no OAuth application to register. Then in Claude go to Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Sign in as yourself when Claude asks and your Mercury connection is ready.
Does Mercury work with ChatGPT and Cursor as well as Claude?
Yes. You connect Mercury once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. Nothing has to be set up again per client.
What can an AI agent actually do with my Mercury data?
It can look across your Mercury accounts, find and explain individual transactions, add notes to them, and set up a payment to a saved recipient. It can also create and update customers, raise and edit invoices, add or update payment recipients, and issue, change or remove cards. Because Mercury has a lot of possible actions, short concrete asks like "list card payments over 500 dollars in March" work better than long paragraphs.
Does connecting Mercury give the AI access to every account and payment?
No. Every request runs inside the Mercury access of the person who signed in, so the AI sees the accounts, cards and transactions that person could already see in Mercury. Elaichi can narrow that further, for example to viewing only, but it can never widen it beyond what Mercury itself allows that person.
Can I stop an agent from creating payments or deleting things in Mercury?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Mercury accounts and transactions while blocking payments, card deletion or invoice changes. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to a Mercury connection when someone leaves?
Offboarding that person in Elaichi ends their access to Mercury through every client at once, with no key to rotate. A shared Mercury connection keeps working for everyone else on the team. If you ever want Mercury gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and the Elaichi Agent together.
Put Mercury in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.