How to connect Mailtrap to OpenClaw
Connect Mailtrap to OpenClaw with ClawLink: paste your Mailtrap key once and 49 tools work from chat. No MCP server to run, nothing stored on your machine.
MailtrapOAUTH2MCPEmail Delivery Platform for testing and sending transactional emails.. Once connected, OpenClaw can read and act on Mailtrap from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Mailtrap 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 Mailtrap setup: install one ClawHub skill, connect Mailtrap in the browser, and OpenClaw can call real Mailtrap 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 Mailtrap.
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 Mailtrap
Enter your account details in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Mailtrap?"
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 Mailtrap in the ClawLink dashboard — enter your Mailtrap account details once.
Verify the connection by asking OpenClaw:
Create it in Mailtrap for me, then confirm the important fields before you finish.
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 Mailtrap is connected in the dashboard, that agent calls the same 49 Mailtrap tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Mailtrap MCP for OpenClaw
Looking for a Mailtrap MCP server for OpenClaw? ClawLink connects Mailtrap to OpenClaw and exposes 49 Mailtrap tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Mailtrap integration works the same way.
What the OpenClaw Mailtrap integration can do
49 Mailtrap tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 49.
30 of 49 Mailtrap tools for OpenClaw
| Tool | What it does |
|---|---|
Create contact export mailtrap_create_contact_export | Create a contact export job for a Mailtrap account |
Get billing usage mailtrap_get_billing_usage | Retrieve current billing cycle usage for an account |
Get contact mailtrap_get_contact | Retrieve a contact by UUID or email address from Mailtrap |
Get contact export mailtrap_get_contact_export | Retrieve the status of a contact export |
Get contact field mailtrap_get_contact_field | Retrieve contact field details by field ID |
Get contact import mailtrap_get_contact_import | Retrieve the status of a contact import operation |
Get contact list mailtrap_get_contact_list | Retrieve a specific contact list by its ID |
Get email template mailtrap_get_email_template | Retrieve details of a specific email template by ID |
Get inbox mailtrap_get_inbox | Retrieve inbox attributes from Mailtrap |
Get message HTML mailtrap_get_message_html | Retrieve the HTML body of a message from Mailtrap |
Get permission resources mailtrap_get_permission_resources | Retrieve all resources in account for permission management |
Get project mailtrap_get_project | Retrieve project details from Mailtrap by project ID |
Get sending domain mailtrap_get_sending_domain | Retrieve sending domain details from Mailtrap |
Get sending stats mailtrap_get_sending_stats | Retrieve email sending statistics from Mailtrap for a specific account |
Get sending stats by categories mailtrap_get_sending_stats_by_categories | Retrieve email sending statistics grouped by categories |
Get sending stats by date mailtrap_get_sending_stats_by_date | Retrieve email sending statistics aggregated by date |
Get sending stats by domains mailtrap_get_sending_stats_by_domains | Retrieve sending statistics grouped by domains for a Mailtrap account |
Get sending stats by esp mailtrap_get_sending_stats_by_esp | Retrieve email sending statistics grouped by email service providers (ESPs) for a specified |
List accounts mailtrap_list_accounts | List all Mailtrap accounts you have access to |
List contact fields mailtrap_list_contact_fields | Get all contact fields for a Mailtrap account |
List contact lists mailtrap_list_contact_lists | Retrieve all contact lists for a Mailtrap account |
List email templates mailtrap_list_email_templates | Retrieve all email templates for a Mailtrap account |
List inboxes mailtrap_list_inboxes | Get a list of inboxes for a Mailtrap account |
List messages mailtrap_list_messages | Get messages from a Mailtrap inbox |
List projects mailtrap_list_projects | Get a list of projects for a Mailtrap account |
List sending domains mailtrap_list_sending_domains | List all sending domains for a Mailtrap account |
List suppressions mailtrap_list_suppressions | List suppressed email addresses for a Mailtrap account |
Create contact mailtrap_create_contact | Create a new contact in Mailtrap |
Create contact event mailtrap_create_contact_event | Create a contact event in Mailtrap |
Create contact field mailtrap_create_contact_field | Create a custom contact field in Mailtrap |
Try it: find the Mailtrap tool you need
Browse the 30 Mailtrap tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Mailtrap for me, then confirm the important fields before you finish.
Pull the relevant data from Mailtrap, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Mailtrap, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Mailtrap, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual credential 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 Mailtrap working from chat.
| Manual | ClawLink | |
|---|---|---|
| Setup flow | Collect and store the right Mailtrap credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link Mailtrap without custom integration screens. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Mailtrap. | 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 Mailtrap actions to the runtime in a format your agent can reliably use. | 49 tools for Mailtrap are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Mailtrap 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 Mailtrap in the browser, and the 49 tools above work from chat. There is no SDK and no config file, and the Mailtrap 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 Mailtrap skill but can't call the tools
The ClawHub skill teaches OpenClaw about Mailtrap, but the calls run through the ClawLink plugin and your connected account. Make sure Mailtrap 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 Mailtrap 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 Mailtrap tools
Mailtrap 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 Mailtrap 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.
Mailtrap 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.
The setup form accepts credentials but calls still fail
Re-enter the credentials carefully and verify the account-level permissions for Mailtrap. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles.
FAQ
Is there a OpenClaw Mailtrap integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Mailtrap: link your Mailtrap account once in the browser and OpenClaw can call the Mailtrap API through 49 ready-made tools — no custom code or token handling.
How do I add Mailtrap to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Mailtrap skill from ClawHub, then you click Connect in the dashboard to authorize Mailtrap. OpenClaw calls the tools from the next message — no config files, and the Mailtrap key you paste is stored server-side instead of in your environment.
How long does it take to connect Mailtrap to OpenClaw?
About two minutes. Sign in, click Connect next to Mailtrap in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Mailtrap up myself?
The alternative to ClawLink is usually manual credential 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 Mailtrap working from chat.
OpenClaw installed the Mailtrap skill but can't call the tools
The ClawHub skill teaches OpenClaw about Mailtrap, but the calls run through the ClawLink plugin and your connected account. Make sure Mailtrap 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.
