# How to connect Mercury to Hermes Agent (no API keys) > Connect Mercury to Hermes with ClawLink in one click — 30 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/mercury Most guides for giving Hermes Agent Mercury access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Mercury setup: pair once in the browser and your always-on Hermes agent can act on Mercury for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Mercury. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Mercury** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect mercury # connect Mercury (browser OAuth) npx -y @useclawlink/cli actions mercury # list available actions npx -y @useclawlink/cli run mercury --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Mercury in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Mercury to mcp get account and walk me through the result in plain English. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Mercury MCP for Hermes Looking for a Mercury MCP server for Hermes Agent? ClawLink connects Mercury to Hermes Agent and exposes 30 Mercury tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Mercury integration](https://claw-link.dev/openclaw/mercury) works the same way. ## What the Hermes Agent Mercury integration can do 30 Mercury tools are ready for Hermes Agent once the account is connected. ### All 30 Mercury tools for Hermes | 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 | ## Example prompts **Mcp Get Account** > Use Mercury to mcp get account and walk me through the result in plain English. **Mcp Get Account Cards** > Use Mercury to mcp get account cards and walk me through the result in plain English. **Mcp Get Account Statements** > Use Mercury to mcp get account statements and walk me through the result in plain English. **Mcp Get Accounts** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Mercury Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Mercury integration? Yes. ClawLink is the fastest way to connect Hermes to Mercury: link your Mercury account once in the browser and Hermes Agent can call the Mercury API through 30 ready-made tools — no custom code or token handling. ### How do I connect Mercury to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Mercury in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Mercury to Hermes Agent? About two minutes. Sign in, click Connect next to Mercury in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Mercury working from chat. ### Hermes paired but still can't use Mercury Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Connect Stripe](https://claw-link.dev/hermes/stripe) — Manage payments, customers, and invoices - [Zoho Books](https://claw-link.dev/hermes/zoho-books) — Organize finances, invoices, bills, and accounting - [Ramp](https://claw-link.dev/hermes/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts