How to connect Mercury to OpenClaw
Connect Mercury to OpenClaw with ClawLink in one click — 30 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
MercuryOAUTH2MCPRead business banking accounts, balances, and transactions. Once connected, OpenClaw can read and act on Mercury from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Mercury access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Mercury setup: install one ClawHub skill, connect Mercury in the browser, and OpenClaw can call real Mercury actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Mercury.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Mercury
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Mercury?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Mercury in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Mercury to mcp get account and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Mercury is connected in the dashboard, that agent calls the same 30 Mercury tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Mercury MCP for OpenClaw
Looking for a Mercury MCP server for OpenClaw? ClawLink connects Mercury to OpenClaw and exposes 30 Mercury tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Mercury integration works the same way.
What the OpenClaw Mercury integration can do
30 Mercury tools are ready for OpenClaw once the account is connected.
All 30 Mercury tools for OpenClaw
| Tool | What it does |
|---|---|
Mcp get account mercury_mcp_get_account | Get account by ID |
Mcp get account cards mercury_mcp_get_account_cards | Retrieve all debit and credit cards associated with a specific account |
Mcp get account statements mercury_mcp_get_account_statements | Retrieve a paginated list of monthly statements for a specific account |
Mcp get accounts mercury_mcp_get_accounts | Retrieve a paginated list of accounts |
Mcp get attachment mercury_mcp_get_attachment | Retrieve attachment details including download URL |
Mcp get current date mercury_mcp_get_current_date | Get the current date in the format |
Mcp get customer mercury_mcp_get_customer | Retrieve details of a specific customer by their ID |
Mcp get invoice mercury_mcp_get_invoice | Retrieve details of an invoice by its ID |
Mcp get organization mercury_mcp_get_organization | Retrieve information about your organization including EIN, legal business name, and DBAs |
Mcp get recipient mercury_mcp_get_recipient | Retrieve details of a specific recipient by ID |
Mcp get recipients mercury_mcp_get_recipients | Retrieve a paginated list of all recipients |
Mcp get safe request mercury_mcp_get_safe_request | Retrieve a specific SAFE request by its ID |
Mcp get safe requests mercury_mcp_get_safe_requests | Retrieve all SAFE (Simple Agreement for Future Equity) requests for your organization |
Mcp get transaction mercury_mcp_get_transaction | Get transaction by ID |
Mcp get transaction by ID mercury_mcp_get_transaction_by_id | Retrieve a single transaction by its ID |
Mcp get treasury mercury_mcp_get_treasury | Retrieve a paginated list of all treasury accounts associated with the authenticated |
Mcp get treasury statements mercury_mcp_get_treasury_statements | Retrieve a paginated list of statements for a specific treasury account |
Mcp get treasury transactions mercury_mcp_get_treasury_transactions | Retrieve paginated treasury transactions for a specific treasury account |
Mcp get user mercury_mcp_get_user | Get user by ID |
Mcp get users mercury_mcp_get_users | Get all users |
Mcp get webhook mercury_mcp_get_webhook | Retrieve details of a specific webhook endpoint by ID |
Mcp get webhooks mercury_mcp_get_webhooks | Retrieve a paginated list of all webhook endpoints for your organization |
Mcp list categories mercury_mcp_list_categories | Retrieve a paginated list of all available custom expense categories for the organization |
Mcp list credit mercury_mcp_list_credit | Retrieve a list of all credit accounts for the organization |
Mcp list customers mercury_mcp_list_customers | Retrieve a paginated list of customers |
Mcp list invoice attachments mercury_mcp_list_invoice_attachments | Retrieve a list of all attachments for a specific invoice |
Mcp list invoices mercury_mcp_list_invoices | Retrieve a paginated list of invoices |
Mcp list recipients attachments mercury_mcp_list_recipients_attachments | Retrieve a paginated list of all recipient tax form attachments across all recipients in the |
Mcp list send money approval requests mercury_mcp_list_send_money_approval_requests | Retrieve a paginated list of send money approval requests for the authenticated organization |
Mcp list transactions mercury_mcp_list_transactions | Retrieve a paginated list of all transactions across all accounts |
Try it: find the Mercury tool you need
Browse the 30 Mercury tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Mercury to mcp get account and walk me through the result in plain English.
Use Mercury to mcp get account cards and walk me through the result in plain English.
Use Mercury to mcp get account statements and walk me through the result in plain English.
Use Mercury to mcp get accounts and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Mercury working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Mercury app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Mercury through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Mercury. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Mercury actions to the runtime in a format your agent can reliably use. | 30 tools for Mercury are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Mercury to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Mercury in the browser, and the 30 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Mercury skill but can't call the tools
The ClawHub skill teaches OpenClaw about Mercury, but the calls run through the ClawLink plugin and your connected account. Make sure Mercury is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Mercury from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Mercury tools
Mercury tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Mercury call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Mercury returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Mercury and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Mercury integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Mercury: link your Mercury account once in the browser and OpenClaw can call the Mercury API through 30 ready-made tools — no custom code or token handling.
How do I add Mercury to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Mercury skill from ClawHub, then you click Connect in the dashboard to authorize Mercury. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Mercury to OpenClaw?
About two minutes. Sign in, click Connect next to Mercury in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Mercury up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Mercury working from chat.
OpenClaw installed the Mercury skill but can't call the tools
The ClawHub skill teaches OpenClaw about Mercury, but the calls run through the ClawLink plugin and your connected account. Make sure Mercury is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
