How to connect MailerSend to Hermes Agent
Connect MailerSend to Hermes with ClawLink: paste your MailerSend key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine.
MailerSendAPI KEYMCPMailerSend is a transactional email service designed for developers to integrate email sending capabilities into their applications.. Once connected, Hermes Agent can read and act on MailerSend from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent MailerSend 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 MailerSend setup: pair once in the browser and your always-on Hermes agent can act on MailerSend 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 MailerSend.
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 MailerSend
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with MailerSend?"
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 MailerSend in the ClawLink dashboard — paste your MailerSend API key once.
Verify the connection by asking Hermes:
Pull the relevant data from MailerSend, 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 MailerSend is connected in the dashboard, that agent calls the same 23 MailerSend tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
MailerSend MCP for Hermes
Looking for a MailerSend MCP server for Hermes Agent? ClawLink connects MailerSend to Hermes Agent and exposes 23 MailerSend tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw MailerSend integration works the same way.
What the Hermes Agent MailerSend integration can do
23 MailerSend tools are ready for Hermes Agent once the account is connected. The 22 below are the ones people reach for most; your agent can call all 23.
22 of 23 MailerSend tools for Hermes
| Tool | What it does |
|---|---|
Get API quota mailersend_get_api_quota | Retrieve current API usage quota |
Get domain mailersend_get_domain | Retrieve detailed information about a specific sending domain in MailerSend |
Get domain recipients mailersend_get_domain_recipients | List recipients for a domain |
Get domains mailersend_get_domains | Retrieve a paginated list of all sending domains configured in your MailerSend account |
Get general resources mailersend_get_general_resources | Retrieve general API resources and information |
Get identities mailersend_get_identities | Retrieves a paginated list of sender identities configured in your MailerSend account |
Get messages mailersend_get_messages | Retrieve a paginated list of sent messages |
Get recipients mailersend_get_recipients | Retrieve a list of email recipients |
Get sms activity mailersend_get_sms_activity | Retrieve SMS activity logs |
Get sms inbounds mailersend_get_sms_inbounds | Retrieve inbound SMS route configurations |
Get sms messages mailersend_get_sms_messages | Retrieves a paginated list of SMS messages sent through the MailerSend API |
Get sms numbers mailersend_get_sms_numbers | Retrieve a paginated list of SMS phone numbers |
Get sms recipients mailersend_get_sms_recipients | Retrieve a list of SMS recipients |
Get smtp users mailersend_get_smtp_users | Retrieve a list of SMTP users |
Get templates mailersend_get_templates | Retrieves a paginated list of email templates from your MailerSend account |
Get tokens mailersend_get_tokens | Retrieves a paginated list of API tokens associated with your MailerSend account |
Get users mailersend_get_users | Retrieve a list of users associated with your account |
Get webhooks mailersend_get_webhooks | Retrieve a list of webhooks |
Create domain mailersend_create_domain | Add a new sending domain to MailerSend |
Create smtp user mailersend_create_smtp_user | Create a new SMTP user |
Create token mailersend_create_token | Creates a new API token with specified scopes (permissions) for a domain |
Create webhook mailersend_create_webhook | Create a new webhook for a MailerSend domain |
Try it: find the MailerSend tool you need
Browse the 22 MailerSend 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 MailerSend, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from MailerSend, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from MailerSend, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from MailerSend, 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 MailerSend working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the MailerSend API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected MailerSend 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 MailerSend. | 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 MailerSend actions to the runtime in a format your agent can reliably use. | 23 tools for MailerSend are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes MailerSend 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 MailerSend in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the MailerSend 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 MailerSend
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 MailerSend 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 MailerSend tools
MailerSend 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 MailerSend 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.
MailerSend 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 MailerSend 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 MailerSend integration?
Yes. ClawLink is the fastest way to connect Hermes to MailerSend: link your MailerSend account once in the browser and Hermes Agent can call the MailerSend API through 23 ready-made tools — no custom code or token handling.
How do I connect MailerSend 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 MailerSend in the dashboard and Hermes can use it from the next message — no config files, and the MailerSend key you paste is stored server-side instead of in your environment.
How long does it take to connect MailerSend to Hermes Agent?
About two minutes. Sign in, click Connect next to MailerSend in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring MailerSend 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 MailerSend working from chat.
Hermes paired but still can't use MailerSend
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.
