Yes — Hermes Agent can set up, tune and monitor email warmup across your mailboxes in WarmySender, all in plain language, through the same 78-tool connection Claude, ChatGPT, Cursor, Codex, OpenClaw, and Hermes Agent share. You ask in Hermes Agent’s chat, configured from ~/.hermes/config.yaml. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
Hermes Agent is configured from a file, and you talk to it in its own chat once the WarmySender block is loaded. It connects through a short block in ~/.hermes/config.yaml; run /reload-mcp in the chat and sign in when prompted. Warmup via Hermes Agent is a good fit for a standing setup: once the config block is in place, checking mailbox health and turning warmup on for a batch is a message in the chat. It reads stats and writes settings; the ramp itself stays with WarmySender.
Every "can" below stands on a real tool in the WarmySender connection. Every "cannot" is not a setting — there is simply nothing an agent can call that does it.
| Can / cannot | What that means for email warmup |
|---|---|
| Can | Turn warmup on for a connected mailbox and choose its strategy and target volume. |
| Can | Apply the same warmup settings across a whole set of mailboxes in one instruction. |
| Can | List your mailboxes and report on each one’s health before you scale up sending. |
| Can | Read how each mailbox’s reputation is building and today’s warmup volume. |
| Can | Move warmed mailboxes onto steady maintenance so warmup keeps running quietly. |
| Cannot | Send the warmup mail itself — WarmySender produces and paces it on a ramp an agent cannot reach. |
| Cannot | Make warmup finish faster or skip a stage — the ramp advances on sending days, not on request. |
| Cannot | Turn warmup on for a mailbox that is not connected. |
| Cannot | Connect a mailbox or see a password — connecting stays in the app. |
| Cannot | Remove the small reference tag in warmup subjects that lets you filter warmup mail out of your inbox. |
Hermes Agent reads a short block in its config file, reloads, and signs in — after that, every WarmySender tool is one sentence away.
Add this to ~/.hermes/config.yaml, then run /reload-mcp in the chat and sign in when prompted.
File: ~/.hermes/config.yaml
mcp_servers:
warmysender:
url: "https://warmysender.com/mcp"
auth: oauthPrefer a key? Create one under Settings › API Keys and choose exactly which permissions it carries, including read-only. With a key, the Hermes Agent route is: Add this to ~/.hermes/config.yaml, then run /reload-mcp in the chat.
Both routes reach the same workspace and stay inside the same safe limits. Every agent's steps live on the AI Agents hub.
Turn warmup on for all twelve new mailboxes with the new-domain strategy.
Which of my mailboxes look weak this week, and why?
Move every mailbox that has been warming for more than six weeks onto maintenance.
How much warmup mail did the outreach@ mailbox send today, and is it arriving?
Turn warmup on for the mailboxes below with the new-domain strategy, then show me their health whenever I ask.
Hermes Agent never sends a message itself and can never raise a limit. Creating or launching a campaign only writes it and hands it to WarmySender's scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits and a gradual ramp — the same protections that apply when a human clicks the buttons. Connecting and disconnecting accounts stays in the app. Account safety always wins.
Yes. Connect Hermes Agent to WarmySender and ask in plain language, in Hermes Agent’s chat, configured from ~/.hermes/config.yaml — it can set up, tune and monitor email warmup across your mailboxes. It never sends a message itself and can never raise a limit: it writes the campaign and hands it to WarmySender’s scheduler, which paces every email, LinkedIn, Instagram and WhatsApp action inside safe limits no matter who is driving. Connecting and disconnecting accounts stays in the app.
Hermes Agent reads a short block in its config file, reloads, and signs in — after that, every WarmySender tool is one sentence away. Add this to ~/.hermes/config.yaml, then run /reload-mcp in the chat and sign in when prompted. The block for ~/.hermes/config.yaml is: mcp_servers: warmysender: url: "https://warmysender.com/mcp" auth: oauth — the server address is https://warmysender.com/mcp. The steps are on this page under "Connect Hermes Agent", and the full install hub for every agent is at /ai-agents.
No. Nothing an agent can call moves a limit — not the warmup ramp, a stage or the ceiling on a mailbox’s daily warmup volume. Hermes Agent can read where you are against a limit and tell you when a pause lifts; WarmySender’s scheduler decides what actually goes out.
No. Connecting and disconnecting accounts stays in the app on purpose — a credential should never pass through an agent or a chat log. Connect the mailbox once in WarmySender; after that Hermes Agent can use it.
No. Warmup rises gradually on its own schedule and the ramp advances on sending days, so a mailbox that was disconnected for a while is simply a few sending days behind. If warmup slows for one mailbox it is usually a safeguard working — WarmySender eases that mailbox back on its own — and neither you nor an agent can lift that slowdown, because the slowdown is the fix.
Under mcp_servers in ~/.hermes/config.yaml, exactly as shown on this page, with the address https://warmysender.com/mcp. Then run /reload-mcp in the chat and sign in when prompted — no restart needed.
Run /reload-mcp in the chat: Hermes Agent reads the file on reload, not on save. Then check the indentation of the block (the file is whitespace-sensitive) and that the address reads exactly https://warmysender.com/mcp.
Yes. Create a key under Settings › API Keys and use the key form of the block on the AI Agents hub; the sign-in form on this page is the one that stores no key in the file.
Last updated: 2026-09-09