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

Send and manage emails through AgentMail. Once connected, Hermes Agent can read and act on AgentMail from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent AgentMail 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 AgentMail setup: pair once in the browser and your always-on Hermes agent can act on AgentMail 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 AgentMail.
- 1
Install 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 AgentMail
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with AgentMail?"
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 AgentMail in the ClawLink dashboard — paste your AgentMail API key once.
Verify the connection by asking Hermes:
Create it in AgentMail for me, then confirm the important fields before you finish.
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 AgentMail is connected in the dashboard, that agent calls the same 93 AgentMail tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
AgentMail MCP for Hermes
Looking for a AgentMail MCP server for Hermes Agent? ClawLink connects AgentMail to Hermes Agent and exposes 93 AgentMail tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw AgentMail integration works the same way.
What the Hermes Agent AgentMail integration can do
93 AgentMail 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 93.
30 of 93 AgentMail tools for Hermes
| Tool | What it does |
|---|---|
Create inbox agent_mail_create_inbox | Create a new AgentMail inbox via API. Returns the inbox_id and email address for sending/receiving messages. Use when provisioning new inboxes for agents or workflows. |
Get message agent_mail_get_message | Retrieve the complete details of a specific email message from an AgentMail inbox. |
List inboxes agent_mail_list_inboxes | List all inboxes available to the authenticated AgentMail account. Use this to discover valid inbox_id values for message operations. |
List messages agent_mail_list_messages | List messages from an AgentMail inbox. Returns a messages array; each message uses message_id and timestamp fields (not id, date, or items). |
Send email agent_mail_send_email | Send an email using AgentMail API |
Batch get messages agent_mail_batch_get_messages | Return metadata for up to 500 messages from one inbox in a single request |
Get agenda agent_mail_get_agenda | Get one page of non-cancelled calendar dates in a UTC window, expanding recurring events and |
Get API key agent_mail_get_api_key | Retrieve API-key metadata without exposing bearer secret values |
Get calendar agent_mail_get_calendar | Get an inbox's US-only calendar settings, event count, and ETag |
Get calendar event agent_mail_get_calendar_event | Get the full current form of a US-only calendar event or recurring-event date, including its |
Get current identity agent_mail_get_current_identity | Return the connected AgentMail identity and its organization, pod, or inbox access boundary |
Get domain agent_mail_get_domain | Return an AgentMail custom domain, its domain and tracking verification statuses, and all |
Get domain setup link agent_mail_get_domain_setup_link | Build a one-click Domain Connect DNS setup link when supported |
Get domain zone file agent_mail_get_domain_zone_file | Download the AgentMail-generated DNS zone file for a custom domain as a bounded binary file |
Get draft agent_mail_get_draft | Retrieve the complete contents and scheduling details of one draft |
Get draft attachment agent_mail_get_draft_attachment | Get a temporary download reference for one draft attachment |
Get file agent_mail_get_file | Get Agent Drive file metadata |
Get inbox agent_mail_get_inbox | Retrieve one AgentMail inbox and its metadata by ID or email address |
Get inbox polling webhook agent_mail_get_inbox_polling_webhook | Get one inbox-scoped polling webhook by webhook_id or client_id |
Get inbox webhook agent_mail_get_inbox_webhook | Get one regular webhook created for a selected AgentMail inbox |
Get inbox webhook headers agent_mail_get_inbox_webhook_headers | List only the names of custom delivery headers on an inbox-scoped regular webhook |
Get message attachment agent_mail_get_message_attachment | Get a temporary download reference for one message attachment |
Get organization agent_mail_get_organization | Return the connected AgentMail organization's identifiers, current inbox and domain counts |
Get pod agent_mail_get_pod | Retrieve one AgentMail pod by its unique ID |
Get pod inbox agent_mail_get_pod_inbox | Get an AgentMail inbox through an explicitly selected pod, preserving the pod tenant boundary |
Get polling webhook agent_mail_get_polling_webhook | Get one organization-level polling webhook by webhook_id or client_id |
Get raw message agent_mail_get_raw_message | Get a temporary download reference for one message's raw RFC 5322 source, including its |
Get thread agent_mail_get_thread | Retrieve one AgentMail thread and a paginated page of its messages |
Get thread attachment agent_mail_get_thread_attachment | Get a temporary download reference for an attachment using its thread and attachment IDs |
Get webhook agent_mail_get_webhook | Get one organization-level webhook configuration by ID |
Try it: find the AgentMail tool you need
Browse the 30 AgentMail tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Create it in AgentMail for me, then confirm the important fields before you finish.
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 AgentMail working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the AgentMail API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected AgentMail 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 AgentMail. | 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 AgentMail actions to the runtime in a format your agent can reliably use. | 93 tools for AgentMail are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes AgentMail 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 AgentMail in the browser, and the 93 tools above work from chat. There is no SDK and no config file, and the AgentMail 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 AgentMail
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 AgentMail 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 AgentMail tools
AgentMail 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 AgentMail 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.
AgentMail 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 AgentMail 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 AgentMail integration?
Yes. ClawLink is the fastest way to connect Hermes to AgentMail: link your AgentMail account once in the browser and Hermes Agent can call the AgentMail API through 93 ready-made tools — no custom code or token handling.
How do I connect AgentMail 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 AgentMail in the dashboard and Hermes can use it from the next message — no config files, and the AgentMail key you paste is stored server-side instead of in your environment.
How long does it take to connect AgentMail to Hermes Agent?
About two minutes. Sign in, click Connect next to AgentMail in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring AgentMail 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 AgentMail working from chat.
Hermes paired but still can't use AgentMail
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.