# How to connect Moco to Hermes Agent (paste one key, 218 tools) > Connect Moco to Hermes with ClawLink: paste your Moco key once and 218 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/moco Most guides for giving Hermes Agent Moco 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 Moco setup: pair once in the browser and your always-on Hermes agent can act on Moco for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — 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. ## Setup It takes three steps to connect Hermes to Moco. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Moco** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **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 moco # connect Moco (browser OAuth) npx -y @useclawlink/cli actions moco # list available actions npx -y @useclawlink/cli run moco --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 Moco in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Moco API key once. Verify the connection by asking Hermes: > Use Moco to activate offer customer approval 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 Moco is connected in the dashboard, that agent calls the same 218 Moco 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). ## Moco MCP for Hermes Looking for a Moco MCP server for Hermes Agent? ClawLink connects Moco to Hermes Agent and exposes 218 Moco 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 Moco integration](https://claw-link.dev/openclaw/moco) works the same way. ## What the Hermes Agent Moco integration can do 218 Moco tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 218. ### 30 of 218 Moco tools for Hermes | Tool | What it does | |---|---| | **Activate offer customer approval** `moco_activate_offer_customer_approval` | Activate customer approval on an offer to generate the offer_document_url | | **Activities list** `moco_activities_list` | Retrieves a list of activities (time entries) from MOCO | | **Activity get** `moco_activity_get` | Retrieve a single activity by ID | | **Activity update** `moco_activity_update` | Update an existing activity | | **Assign offer** `moco_assign_offer` | Assign an offer to a project, company, or deal | | **Assign purchase to project** `moco_assign_purchase_to_project` | Assign a purchase item to a project by creating or linking to an expense | | **Comments list** `moco_comments_list` | Retrieve a list of comments | | **Contacts list** `moco_contacts_list` | Retrieve a list of contacts | | **Deal categories list** `moco_deal_categories_list` | Retrieves all deal categories configured in MOCO with their IDs, names, probabilities, and timestamps | | **Deal get** `moco_deal_get` | Retrieves detailed information for a specific deal/lead by its ID from MOCO | | **Deals list** `moco_deals_list` | Retrieve a list of all deals (leads) | | **Get account catalog services items** `moco_get_account_catalog_services_items` | Retrieve a specific item within a catalog service in MOCO | | **Get account fixed costs** `moco_get_account_fixed_costs` | Retrieve all fixed costs from the account | | **Get cashflow** `moco_get_cashflow` | Retrieve the cashflow report from MOCO | | **Get comment** `moco_get_comment` | Retrieve a single comment by ID | | **Get company** `moco_get_company` | Retrieve a single company by ID from MOCO | | **Get contact** `moco_get_contact` | Retrieve detailed information for a specific contact person by ID from MOCO | | **Get custom property** `moco_get_custom_property` | Retrieve a single custom property by ID from MOCO | | **Get deal category** `moco_get_deal_category` | Retrieve a single deal category by ID | | **Get employment** `moco_get_employment` | Retrieve a single employment (weekly work model) by ID | | **Get holiday** `moco_get_holiday` | Retrieve a single holiday entry by ID | | **Get internal hourly rates** `moco_get_internal_hourly_rates` | Retrieve all internal hourly rates from the account | | **Get invoice** `moco_get_invoice` | Retrieve a single invoice by ID with full details including items, payments, and reminders | | **Get invoice bookkeeping export** `moco_get_invoice_bookkeeping_export` | Retrieve a single invoice bookkeeping export by ID | | **Get invoice payment** `moco_get_invoice_payment` | Retrieve a single invoice payment by ID | | **Get invoice reminder** `moco_get_invoice_reminder` | Retrieve a single invoice reminder by ID | | **Get invoice reminders** `moco_get_invoice_reminders` | Retrieve all invoice reminders | | **Get invoice timesheet** `moco_get_invoice_timesheet` | Retrieve a time sheet for a particular invoice, i.e | | **Get invoices bookkeeping exports** `moco_get_invoices_bookkeeping_exports` | Retrieve all invoice bookkeeping exports | | **Get invoices expenses** `moco_get_invoices_expenses` | Retrieve all expenses that were invoiced in a particular invoice | ## Example prompts **Activate Offer Customer Approval** > Use Moco to activate offer customer approval and walk me through the result in plain English. **Activities List** > Use Moco to activities list and walk me through the result in plain English. **Activity Get** > Use Moco to activity get and walk me through the result in plain English. **Activity Update** > Use Moco to activity update and walk me through the result in plain English. ## 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 Moco working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Moco API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Moco 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 Moco. | 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 Moco actions to the runtime in a format your agent can reliably use. | 218 tools for Moco are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Moco 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 Moco in the browser, and the 218 tools above work from chat. There is no SDK and no config file, and the Moco 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 Moco 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 Moco 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 Moco tools Moco 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 Moco 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. ### Moco 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 Moco 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 Moco integration? Yes. ClawLink is the fastest way to connect Hermes to Moco: link your Moco account once in the browser and Hermes Agent can call the Moco API through 218 ready-made tools — no custom code or token handling. ### How do I connect Moco 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 Moco in the dashboard and Hermes can use it from the next message — no config files, and the Moco key you paste is stored server-side instead of in your environment. ### How long does it take to connect Moco to Hermes Agent? About two minutes. Sign in, click Connect next to Moco in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Moco 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 Moco working from chat. ### Hermes paired but still can't use Moco 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 - [DocuSign](https://claw-link.dev/hermes/docusign) — Send, sign, and manage agreements and envelopes - [Trello tools](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards - [Hermes ClickUp integration](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints