How to connect ManyReach to Hermes Agent
Connect ManyReach to Hermes with ClawLink: paste your ManyReach key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.


ManyReach is a cold email outreach platform for managing campaigns, prospects, senders, messages, and workspaces.. Once connected, Hermes Agent can read and act on ManyReach from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent ManyReach 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 ManyReach setup: pair once in the browser and your always-on Hermes agent can act on ManyReach 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 ManyReach.
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 ManyReach
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with ManyReach?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect ManyReach in the ClawLink dashboard — paste your ManyReach API key once.
Verify the connection by asking Hermes:
Pull the relevant data from ManyReach, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once ManyReach is connected in the dashboard, that agent calls the same 16 ManyReach tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
ManyReach MCP for Hermes
Looking for a ManyReach MCP server for Hermes Agent? ClawLink connects ManyReach to Hermes Agent and exposes 16 ManyReach tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw ManyReach integration works the same way.
What the Hermes Agent ManyReach integration can do
16 ManyReach tools are ready for Hermes Agent once the account is connected. The 15 below are the ones people reach for most; your agent can call all 16.
15 of 16 ManyReach tools for Hermes
| Tool | What it does |
|---|---|
Get account overview manyreach_get_account_overview | Return the authenticated ManyReach organization together with its sending-credit and data-token |
List campaigns manyreach_list_campaigns | Find campaigns in the authenticated organization, optionally filtering by lifecycle status or |
List lists manyreach_list_lists | Return one page of mailing lists available for organizing and importing prospects |
List messages manyreach_list_messages | Retrieve one read-only page of reply, sent, or manually sent messages with campaign, followup |
List prospects manyreach_list_prospects | Search and filter prospects by identity, CRM status, tags, campaign membership, and existing |
List senders manyreach_list_senders | Find configured sender mailboxes by folder, connection status, warmup state, or search text |
List tags manyreach_list_tags | Find CRM, campaign, or sender tags and optionally include prospect counts |
Create campaign manyreach_create_campaign | Create and save a new draft campaign's configuration |
Create list manyreach_create_list | Create a ManyReach mailing list |
Create prospect manyreach_create_prospect | Create one ManyReach prospect |
Create tag manyreach_create_tag | Create a CRM, campaign, or sender tag |
Update campaign manyreach_update_campaign | Update an existing draft campaign's configuration |
Update list manyreach_update_list | Rename or move an existing ManyReach mailing list |
Update prospect manyreach_update_prospect | Update contact, personalization, list, CRM, or campaign-sending eligibility fields for one |
Update tag manyreach_update_tag | Update an existing tag's title and description |
Try it: find the ManyReach tool you need
Browse the 15 ManyReach tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from ManyReach, summarize it in plain English, and point out anything that needs attention.
List the relevant items in ManyReach, group them by priority, and recommend what Hermes should do next.
List the relevant items in ManyReach, group them by priority, and recommend what Hermes should do next.
List the relevant items in ManyReach, group them by priority, and recommend what Hermes should do next.
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 ManyReach working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the ManyReach API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected ManyReach 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 ManyReach. | 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 ManyReach actions to the runtime in a format your agent can reliably use. | 16 tools for ManyReach are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes ManyReach 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 ManyReach in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the ManyReach key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use ManyReach
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 ManyReach 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 ManyReach tools
ManyReach 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 ManyReach 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.
ManyReach 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 ManyReach has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent ManyReach integration?
Yes. ClawLink is the fastest way to connect Hermes to ManyReach: link your ManyReach account once in the browser and Hermes Agent can call the ManyReach API through 16 ready-made tools — no custom code or token handling.
How do I connect ManyReach 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 ManyReach in the dashboard and Hermes can use it from the next message — no config files, and the ManyReach key you paste is stored server-side instead of in your environment.
How long does it take to connect ManyReach to Hermes Agent?
About two minutes. Sign in, click Connect next to ManyReach in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring ManyReach 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 ManyReach working from chat.
Hermes paired but still can't use ManyReach
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.