# How to connect ManyReach to OpenClaw (paste one key, 16 tools) > Connect ManyReach to OpenClaw with ClawLink: paste your ManyReach key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/manyreach The usual route to ManyReach access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical ManyReach setup: install one ClawHub skill, connect ManyReach in the browser, and OpenClaw can call real ManyReach actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to ManyReach. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect ManyReach** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 manyreach # connect ManyReach (browser OAuth) npx -y @useclawlink/cli actions manyreach # list available actions npx -y @useclawlink/cli run manyreach --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect ManyReach in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your ManyReach API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from ManyReach, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw 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 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## ManyReach MCP for OpenClaw Looking for a ManyReach MCP server for OpenClaw? ClawLink connects ManyReach to OpenClaw and exposes 16 ManyReach 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 Hermes instead? The [Hermes ManyReach integration](https://claw-link.dev/hermes/manyreach) works the same way. ## What the OpenClaw ManyReach integration can do 16 ManyReach tools are ready for OpenClaw 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 OpenClaw | 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 | ## Example prompts **Get Account Overview** > Pull the relevant data from ManyReach, summarize it in plain English, and point out anything that needs attention. **List Campaigns** > List the relevant items in ManyReach, group them by priority, and recommend what OpenClaw should do next. **List Lists** > List the relevant items in ManyReach, group them by priority, and recommend what OpenClaw should do next. **List Messages** > List the relevant items in ManyReach, group them by priority, and recommend what OpenClaw 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 OpenClaw. 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 OpenClaw 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the ManyReach skill but can't call the tools The ClawHub skill teaches OpenClaw about ManyReach, but the calls run through the ClawLink plugin and your connected account. Make sure ManyReach is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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. ### Is there a OpenClaw ManyReach integration? Yes. ClawLink is the fastest way to connect OpenClaw to ManyReach: link your ManyReach account once in the browser and OpenClaw can call the ManyReach API through 16 ready-made tools — no custom code or token handling. ### How do I add ManyReach to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink ManyReach skill from ClawHub, then you click Connect in the dashboard to authorize ManyReach. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to ManyReach in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want ManyReach working from chat. ### OpenClaw installed the ManyReach skill but can't call the tools The ClawHub skill teaches OpenClaw about ManyReach, but the calls run through the ClawLink plugin and your connected account. Make sure ManyReach is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [OpenClaw Benchmark Email integration](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp tools](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences