# How to connect Chaser to Hermes Agent (paste one key, 30 tools) > Connect Chaser to Hermes with ClawLink: paste your Chaser key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/chaser Most guides for giving Hermes Agent Chaser 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 Chaser setup: pair once in the browser and your always-on Hermes agent can act on Chaser 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 Chaser. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Chaser** — 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 chaser # connect Chaser (browser OAuth) npx -y @useclawlink/cli actions chaser # list available actions npx -y @useclawlink/cli run chaser --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 Chaser in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Chaser API key once. Verify the connection by asking Hermes: > Pull the relevant data from Chaser, summarize it in plain English, and point out anything that needs attention. ### 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 Chaser is connected in the dashboard, that agent calls the same 30 Chaser 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). ## Chaser MCP for Hermes Looking for a Chaser MCP server for Hermes Agent? ClawLink connects Chaser to Hermes Agent and exposes 30 Chaser 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 Chaser integration](https://claw-link.dev/openclaw/chaser) works the same way. ## What the Hermes Agent Chaser integration can do 30 Chaser tools are ready for Hermes Agent once the account is connected. The 29 below are the ones people reach for most; your agent can call all 30. ### 29 of 30 Chaser tools for Hermes | Tool | What it does | |---|---| | **Get contact person** `chaser_get_contact_person` | Get a specific contact person by ID for a customer | | **Get credit note by ID** `chaser_get_credit_note_by_id` | Retrieve detailed information for a specific credit note by its ID | | **Get credit notes** `chaser_get_credit_notes` | Retrieves a list of credit notes from Chaser | | **Get current organisation** `chaser_get_current_organisation` | Retrieve information about the current organisation associated with the API credentials | | **Get customer by ID** `chaser_get_customer_by_id` | Retrieve detailed information for a specific customer by their Chaser customer ID | | **Get customers** `chaser_get_customers` | Retrieve a list of all customers associated with the organization | | **Get invoice** `chaser_get_invoice` | Retrieve detailed information for a specific invoice by its ID | | **Get organization** `chaser_get_organization` | Retrieve information about the connected organizations | | **Get overpayment** `chaser_get_overpayment` | Retrieve detailed information for a specific overpayment by its ID | | **Get status** `chaser_get_status` | Check the status of the Chaser API | | **List contact persons** `chaser_list_contact_persons` | Retrieve contact persons for a specific customer | | **List invoices** `chaser_list_invoices` | Retrieve invoices with pagination and filtering | | **List overpayments** `chaser_list_overpayments` | Retrieve overpayments from Chaser with pagination and filtering | | **Create contact person** `chaser_create_contact_person` | Create a new contact person for a customer in Chaser | | **Create invoice** `chaser_create_invoice` | Create a new invoice record in the organization | | **Create overpayment** `chaser_create_overpayment` | Creates a new overpayment record in Chaser for tracking customer overpayments | | **Post credit note** `chaser_post_credit_note` | Creates a new credit note record in Chaser for tracking customer credits | | **Post customer** `chaser_post_customer` | Create a new customer record in Chaser | | **Put credit note** `chaser_put_credit_note` | Update an existing credit note in Chaser | | **Put customer** `chaser_put_customer` | Update an existing customer's information using their unique Chaser customer ID | | **Put invoice** `chaser_put_invoice` | Update an existing invoice in Chaser by its internal ID | | **Update contact person** `chaser_update_contact_person` | Update a contact person for a customer in Chaser | | **Update overpayment** `chaser_update_overpayment` | Update an overpayment record in Chaser | | **Upload invoice PDF** `chaser_upload_invoice_pdf` | Upload a PDF file to an existing invoice in Chaser | | **Upsert bulk customers** `chaser_upsert_bulk_customers` | Bulk upsert up to 100 customers in a single operation | | **Upsert contact persons** `chaser_upsert_contact_persons` | Bulk insert or update contact persons for a customer | | **Upsert credit notes bulk** `chaser_upsert_credit_notes_bulk` | Bulk upsert up to 100 credit notes in a single request | | **Upsert invoices** `chaser_upsert_invoices` | Bulk upsert up to 100 invoices in a single request | | **Upsert overpayments bulk** `chaser_upsert_overpayments_bulk` | Bulk upsert up to 100 overpayments in Chaser, matching by overpayment_id | ## Example prompts **Get Contact Person** > Pull the relevant data from Chaser, summarize it in plain English, and point out anything that needs attention. **Get Credit Note By Id** > Pull the relevant data from Chaser, summarize it in plain English, and point out anything that needs attention. **Get Credit Notes** > Pull the relevant data from Chaser, summarize it in plain English, and point out anything that needs attention. **Get Current Organisation** > Pull the relevant data from Chaser, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Chaser working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Chaser API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Chaser account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Chaser. | 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 Chaser actions to the runtime in a format your agent can reliably use. | 30 tools for Chaser are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Chaser 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 Chaser in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Chaser key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Chaser 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 Chaser 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 Chaser tools Chaser 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 Chaser 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. ### Chaser 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. ### API key setup works but results look incomplete Double-check that the API key for Chaser has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Chaser integration? Yes. ClawLink is the fastest way to connect Hermes to Chaser: link your Chaser account once in the browser and Hermes Agent can call the Chaser API through 30 ready-made tools — no custom code or token handling. ### How do I connect Chaser 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 Chaser in the dashboard and Hermes can use it from the next message — no config files, and the Chaser key you paste is stored server-side instead of in your environment. ### How long does it take to connect Chaser to Hermes Agent? About two minutes. Sign in, click Connect next to Chaser in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Chaser up myself? The alternative to ClawLink is usually manual API key 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 Chaser working from chat. ### Hermes paired but still can't use Chaser 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