How to connect MailSlurp to OpenClaw
Connect MailSlurp to OpenClaw with ClawLink: paste your MailSlurp key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
MailSlurpAPI KEYMCPMailSlurp provides programmable email and SMS inboxes, sending, testing, webhooks, and deliverability tools through a REST API.. Once connected, OpenClaw can read and act on MailSlurp from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to MailSlurp 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 MailSlurp setup: install one ClawHub skill, connect MailSlurp in the browser, and OpenClaw can call real MailSlurp 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 MailSlurp.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect MailSlurp
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with MailSlurp?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 MailSlurp in the ClawLink dashboard — paste your MailSlurp API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from MailSlurp, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once MailSlurp is connected in the dashboard, that agent calls the same 14 MailSlurp tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
MailSlurp MCP for OpenClaw
Looking for a MailSlurp MCP server for OpenClaw? ClawLink connects MailSlurp to OpenClaw and exposes 14 MailSlurp tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes MailSlurp integration works the same way.
What the OpenClaw MailSlurp integration can do
14 MailSlurp tools are ready for OpenClaw once the account is connected. The 13 below are the ones people reach for most; your agent can call all 14.
13 of 14 MailSlurp tools for OpenClaw
| Tool | What it does |
|---|---|
Get account info mailslurp_get_account_info | Return the connected MailSlurp account identity, state, account type, subscription type, and |
Get inbox mailslurp_get_inbox | Get one MailSlurp inbox by UUID, including its email address, type, labels, and lifecycle state |
List contact groups mailslurp_list_contact_groups | List saved MailSlurp contact groups with optional creation-time filters |
List contacts mailslurp_list_contacts | List saved MailSlurp contacts with optional search and creation-time filters |
List domains mailslurp_list_domains | List custom domains configured for the connected MailSlurp account, including identifiers |
List emails mailslurp_list_emails | List received emails across the account or one selected inbox with unread, exact-search |
List inboxes mailslurp_list_inboxes | List MailSlurp inboxes with optional search, tag, type, domain, favorite, and creation-time |
List sent emails mailslurp_list_sent_emails | List sent-email records, optionally filtered by source inbox, exact identifier/address search |
List templates mailslurp_list_templates | List saved MailSlurp email templates with optional creation-time filters |
Create inbox mailslurp_create_inbox | Create a MailSlurp HTTP or SMTP inbox |
Get email mailslurp_get_email | Get one fully hydrated received email by UUID, including parsed headers, body content |
Update inbox mailslurp_update_inbox | Update an inbox's name, description, tags, expiration, or favorite status |
Send email mailslurp_send_email | Send an email from a specific MailSlurp inbox to addresses, saved contacts, or one contact group |
Try it: find the MailSlurp tool you need
Browse the 13 MailSlurp tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from MailSlurp, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from MailSlurp, summarize it in plain English, and point out anything that needs attention.
List the relevant items in MailSlurp, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in MailSlurp, 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 MailSlurp working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the MailSlurp API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected MailSlurp 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 MailSlurp. | 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 MailSlurp actions to the runtime in a format your agent can reliably use. | 14 tools for MailSlurp are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes MailSlurp 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 MailSlurp in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the MailSlurp 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
OpenClaw installed the MailSlurp skill but can't call the tools
The ClawHub skill teaches OpenClaw about MailSlurp, but the calls run through the ClawLink plugin and your connected account. Make sure MailSlurp 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 MailSlurp 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 MailSlurp tools
MailSlurp 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 MailSlurp 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.
MailSlurp 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 MailSlurp has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw MailSlurp integration?
Yes. ClawLink is the fastest way to connect OpenClaw to MailSlurp: link your MailSlurp account once in the browser and OpenClaw can call the MailSlurp API through 14 ready-made tools — no custom code or token handling.
How do I add MailSlurp to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink MailSlurp skill from ClawHub, then you click Connect in the dashboard to authorize MailSlurp. OpenClaw calls the tools from the next message — no config files, and the MailSlurp key you paste is stored server-side instead of in your environment.
How long does it take to connect MailSlurp to OpenClaw?
About two minutes. Sign in, click Connect next to MailSlurp in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring MailSlurp 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 MailSlurp working from chat.
OpenClaw installed the MailSlurp skill but can't call the tools
The ClawHub skill teaches OpenClaw about MailSlurp, but the calls run through the ClawLink plugin and your connected account. Make sure MailSlurp 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.
