How to connect Moneybird to Hermes Agent
Connect Moneybird to Hermes Agent with ClawLink: 21 tools from chat via hosted OAuth. No OAuth app to create, no MCP server to run.
MoneybirdOAUTH2MCPManage invoices, expenses, and accounting for small businesses. Once connected, Hermes Agent can read and act on Moneybird from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Moneybird 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 Moneybird setup: pair once in the browser and your always-on Hermes agent can act on Moneybird for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
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. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
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.Setup
It takes three steps to connect Hermes to Moneybird.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Moneybird
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Moneybird?"
The whole pairing handshake. Run these once, then approve Moneybird in the dashboard:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # approve the link in your browser
hermes clawlink finish
hermes clawlink testThis is the flow Google's AI Overview quotes for this query, so treat the commands as fixed. hermes clawlink test confirms pairing worked; if it fails, run hermes clawlink begin again for a fresh link.
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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Moneybird is connected in the dashboard, that agent calls the same 21 Moneybird tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Moneybird MCP for Hermes
Looking for a Moneybird MCP server for Hermes Agent? ClawLink connects Moneybird to Hermes Agent and exposes 21 Moneybird tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Moneybird integration works the same way.
Moneybird's own docs answer 'no API keys' with OAuth flows and an official MCP server, and search engines teach tool routers like Composio for the hosted part. The alternative Google already lists as the 'ClawLink Method' is this: one-click hosted OAuth. You approve the connection in the browser, pair Hermes with two commands, and the 21 Moneybird tools are in chat. No administration to create, no OAuth app to register, no MCP server to run, and the connection revokes from one dashboard.
What the Hermes Agent Moneybird integration can do
21 Moneybird tools are ready for Hermes Agent once the account is connected. The 18 below are the ones people reach for most; your agent can call all 21.
18 of 21 Moneybird tools for Hermes
| Tool | What it does |
|---|---|
Filter contacts moneybird_filter_contacts | Filter contacts |
Get additional charges moneybird_get_additional_charges | Get additional charges for a contact |
Get contact moneybird_get_contact | Retrieve all information about a specific contact by ID |
Get contact by customer ID moneybird_get_contact_by_customer_id | Retrieve full contact details by customer ID |
Get contact person moneybird_get_contact_person | Get all information about a contact person |
Get sales invoice moneybird_get_sales_invoice | Get a single sales invoice by ID |
List administrations moneybird_list_administrations | List all administrations accessible by the authenticated user |
List contacts synchronization moneybird_list_contacts_synchronization | List all contact IDs and versions for synchronization |
List sales invoices moneybird_list_sales_invoices | List all sales invoices in an administration |
Add note to contact moneybird_add_note_to_contact | Add a note or to-do to a contact |
Create contact moneybird_create_contact | Create a new contact in Moneybird |
Create contact person moneybird_create_contact_person | Create a new contact person |
Create sales invoice moneybird_create_sales_invoice | Create a new sales invoice |
Request contact payments mandate URL moneybird_request_contact_payments_mandate_url | Request a URL for setting up a Payments mandate |
Update contact moneybird_update_contact | Update a contact |
Update contact person moneybird_update_contact_person | Update a contact person |
Update sales invoice moneybird_update_sales_invoice | Update an existing sales invoice by ID |
Archive contact moneybird_archive_contact | Archive a contact |
Try it: find the Moneybird tool you need
Browse the 18 Moneybird tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
List sales invoices with moneybird_list_sales_invoices and split them by paid and unpaid. For unpaid ones older than 30 days, pull the contact with moneybird_get_contact.
Create a sales invoice with moneybird_create_sales_invoice for <contact> with the line items I describe, and show me the total before it is finalised.
Use moneybird_filter_contacts to find contacts with no email address and tell me how many there are per country.
Get contact <id> with moneybird_get_contact and add a note about our last call with moneybird_add_note_to_contact.
How the Moneybird tools behave
A deliberately small toolset; these are the details that decide whether it answers or stalls.
- Small, deliberate toolset. 21 tools: contacts, sales invoices, and administrations are the core, and every write is a real billing or bookkeeping action.
- One administration at a time. Tools act on the administration the connection authorized;
moneybird_list_administrationsshows which ones you can reach. - Customer-id lookups exist.
moneybird_get_contact_by_customer_idmaps an external id to the Moneybird contact, handy when the id came from a shop or CRM. - Invoices are updatable, not just readable.
moneybird_update_sales_invoiceadjusts an existing invoice; worth a confirmation step. - Payment mandates are reachable.
moneybird_request_contact_payments_mandate_urlfetches the mandate URL for direct-debit collection.
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 Moneybird working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Moneybird app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Moneybird 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 Moneybird. | 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 Moneybird actions to the runtime in a format your agent can reliably use. | 21 tools for Moneybird are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Moneybird 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 Moneybird in the browser, and the 21 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
Hermes paired but still can't use Moneybird
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 Moneybird 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 Moneybird tools
Moneybird 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 Moneybird 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.
Moneybird 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.
Moneybird returns 403 or "insufficient permissions"
The engines teach that the token is valid but lacks the scope for the endpoint, with wrong administration and placeholder values as the companion causes, and ChatGPT's permission-error answers match this page's accordion exactly: missing API scopes, wrong administration, placeholder values. In a hosted flow the same three appear: the administration the connection authorized does not cover the object, or the agent passed an id from documentation. Check the administration and the id before reconnecting, which is the fix nobody needs in a hosted flow.
Ask the agent to diagnose it:
Call moneybird_list_administrations and tell me which administration this connection acts on. Then quote the exact error from the failed call. Do not retry it yet.Moneybird results look incomplete
When reads succeed but a list comes back shorter than expected, the cause is usually access rather than absence: the connection's administration or its scopes do not cover everything you expect to see. Ask the agent which administration it is acting on and whether the tool returned a count or a limit marker. This is distinct from the rate-limit shape, where calls start failing outright rather than returning partial lists.
Ask the agent to diagnose it:
Tell me which Moneybird administration you are acting on and which tool returned the short list. Quote the result count you got versus what you expected. Do not retry the call yet.'Tool not found' or Moneybird tools missing
The taught fix for this symptom assumes a config file: check your config, verify your API credentials, restart your application. There is no config file here. The hosted causes are pairing incomplete, fixed by rerunning hermes clawlink begin and hermes clawlink finish and confirming Moneybird shows as connected; schemas loading on demand, so the opening call in a fresh session can arrive before the catalog and needs one retry; and a wrong tool name, where the error lists the closest real ones.
Ask the agent to diagnose it:
List the Moneybird tools you actually have access to. If there are none, say so plainly. If there are, tell me which one lists sales invoices and use that exact name.OAuth finished in the browser but the account is still missing
Try reconnecting Moneybird 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 Hermes Agent Moneybird integration?
Yes. ClawLink is the fastest way to connect Hermes to Moneybird: link your Moneybird account once in the browser and Hermes Agent can call the Moneybird API through 21 ready-made tools — no custom code or token handling.
How do I connect Moneybird 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 Moneybird 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 Moneybird to Hermes Agent?
About two minutes. Sign in, click Connect next to Moneybird in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Moneybird 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 Moneybird working from chat.
Do I need to create a Moneybird OAuth app or administration?
No. The OAuth-app decision is the first thing the engines push you toward, and Moneybird's own 'Moneybird for agents' page wins that conversation. The hosted route has no app on your side: the connection authorizes against the administration you choose during approval, and the tools act on it from there. No client id, no client secret, no token in an env file.
What can the agent do in Moneybird?
Contacts, contact persons, sales invoices, notes on contacts, administrations, customer-id lookups, and payment mandate URLs, plus the writes: create and update contacts, contact persons, and sales invoices, and archive contacts. Creating a sales invoice is a real billing action, so confirm line items and totals.
How is this different from the official Moneybird MCP server?
The official server is self-hosted: you run it and point a client at it. This is the hosted version: no server process on your machine, no client config file, and the tools already wired into a Hermes pairing. The data and the API underneath are the same; the difference is who runs the plumbing and where the credential lives.
Where does the OAuth token live, and how do I revoke it?
Server-side, on the hosted connection. There is no token file on your machine, which is the practical difference from the personal-token route Moneybird's API otherwise uses. Revoke from the ClawLink dashboard, or revoke the app inside Moneybird, and the agent loses access from that moment.
What can it answer about the money side?
Sales invoices can be listed and pulled with their contact details, so 'what is outstanding and from whom' is a direct question. The toolset is deliberately small: it does not replace Moneybird's reporting, it answers the questions you can ask in chat without opening the app.
Hermes paired but still can't use Moneybird
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.
