# How to connect Mailcoach to Hermes Agent (paste one key, 56 tools)

> Connect Mailcoach to Hermes with ClawLink: paste your Mailcoach key once and 56 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/mailcoach

Most guides for giving Hermes Agent Mailcoach 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 Mailcoach setup: pair once in the browser and your always-on Hermes agent can act on Mailcoach 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 Mailcoach.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Mailcoach** — 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 mailcoach  # connect Mailcoach (browser OAuth)
npx -y @useclawlink/cli actions mailcoach  # list available actions
npx -y @useclawlink/cli run mailcoach <action> --input '<json>'  # 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 Mailcoach in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Mailcoach API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from Mailcoach, 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 Mailcoach is connected in the dashboard, that agent calls the same 56 Mailcoach 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).

## Mailcoach MCP for Hermes

Looking for a Mailcoach MCP server for Hermes Agent? ClawLink connects Mailcoach to Hermes Agent and exposes 56 Mailcoach 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 Mailcoach integration](https://claw-link.dev/openclaw/mailcoach) works the same way.

## What the Hermes Agent Mailcoach integration can do

56 Mailcoach 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 56.

### 30 of 56 Mailcoach tools for Hermes

| Tool | What it does |
|---|---|
| **Get all campaigns** `mailcoach_get_all_campaigns` | Retrieve all campaigns |
| **Get all sent items** `mailcoach_get_all_sent_items` | Retrieve all sent items |
| **Get all subscriber imports** `mailcoach_get_all_subscriber_imports` | Retrieve all subscriber imports |
| **Get all suppressions** `mailcoach_get_all_suppressions` | Retrieve a paginated list of all email suppression entries from Mailcoach |
| **Get all tags** `mailcoach_get_all_tags` | Retrieve all tags for a specific email list |
| **Get all templates** `mailcoach_get_all_templates` | Retrieve all templates |
| **Get all transactional email templates** `mailcoach_get_all_transactional_email_templates` | Retrieve all transactional email templates |
| **Get campaign bounces** `mailcoach_get_campaign_bounces` | Retrieve bounced subscribers of a sent campaign with pagination support |
| **Get campaign clicks** `mailcoach_get_campaign_clicks` | Retrieve clicks from a sent campaign with pagination support |
| **Get campaign opens** `mailcoach_get_campaign_opens` | Retrieve all opens for a sent campaign with pagination support |
| **Get campaign unsubscribes** `mailcoach_get_campaign_unsubscribes` | Retrieve unsubscribes from a sent campaign with pagination support |
| **Get email lists** `mailcoach_get_email_lists` | Retrieve all email lists |
| **Get segment** `mailcoach_get_segment` | Retrieve details of a specific segment |
| **Get specific campaign** `mailcoach_get_specific_campaign` | Retrieve details of a specific Mailcoach campaign |
| **Get specific email list** `mailcoach_get_specific_email_list` | Retrieve detailed information about a specific Mailcoach email list by its UUID |
| **Get specific subscriber** `mailcoach_get_specific_subscriber` | Retrieve a specific subscriber |
| **Get specific suppression** `mailcoach_get_specific_suppression` | Retrieve a specific suppression entry |
| **Get specific tag** `mailcoach_get_specific_tag` | Retrieve details of a specific tag |
| **Get specific template** `mailcoach_get_specific_template` | Retrieves the full details of a specific Mailcoach email template by its UUID |
| **Get subscriber import** `mailcoach_get_subscriber_import` | Retrieve details of a specific subscriber import by UUID |
| **Get transactional mail** `mailcoach_get_transactional_mail` | Retrieve details of a specific transactional email by its UUID |
| **Get user** `mailcoach_get_user` | Retrieve details of the currently authenticated user |
| **List segments** `mailcoach_list_segments` | Retrieve all segments for a specific email list |
| **List subscribers** `mailcoach_list_subscribers` | List all subscribers from a specific email list with pagination support |
| **List transactional mails** `mailcoach_list_transactional_mails` | Retrieve all transactional email records |
| **Add campaign** `mailcoach_add_campaign` | Create a new Mailcoach campaign |
| **Add email list** `mailcoach_add_email_list` | Create a new email list |
| **Add suppression** `mailcoach_add_suppression` | Add a suppression entry |
| **Add tag** `mailcoach_add_tag` | Create a new tag within a specific email list |
| **Add tags to subscriber** `mailcoach_add_tags_to_subscriber` | Add tags to a subscriber for segmentation and targeting |

## Example prompts

**Get All Campaigns**

> Pull the relevant data from Mailcoach, summarize it in plain English, and point out anything that needs attention.

**Get All Sent Items**

> Pull the relevant data from Mailcoach, summarize it in plain English, and point out anything that needs attention.

**Get All Subscriber Imports**

> Pull the relevant data from Mailcoach, summarize it in plain English, and point out anything that needs attention.

**Get All Suppressions**

> Pull the relevant data from Mailcoach, 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 Mailcoach working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Mailcoach API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Mailcoach 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 Mailcoach. | 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 Mailcoach actions to the runtime in a format your agent can reliably use. | 56 tools for Mailcoach are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Mailcoach 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 Mailcoach in the browser, and the 56 tools above work from chat. There is no SDK and no config file, and the Mailcoach 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 Mailcoach
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 Mailcoach 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 Mailcoach tools
Mailcoach 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 Mailcoach 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.

### Mailcoach 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 Mailcoach 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 Mailcoach integration?
Yes. ClawLink is the fastest way to connect Hermes to Mailcoach: link your Mailcoach account once in the browser and Hermes Agent can call the Mailcoach API through 56 ready-made tools — no custom code or token handling.

### How do I connect Mailcoach 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 Mailcoach in the dashboard and Hermes can use it from the next message — no config files, and the Mailcoach key you paste is stored server-side instead of in your environment.

### How long does it take to connect Mailcoach to Hermes Agent?
About two minutes. Sign in, click Connect next to Mailcoach in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Mailcoach 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 Mailcoach working from chat.

### Hermes paired but still can't use Mailcoach
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

- [ActiveCampaign](https://claw-link.dev/hermes/activecampaign) — Marketing automation, CRM, and email marketing
- [Benchmark Email](https://claw-link.dev/hermes/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns.
- [Mailchimp](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences