Mailtrap MCP connector
The Mailtrap connector lets Claude, ChatGPT, Cursor, or any MCP client read Mailtrap email logs, sending stats, suppressions, domains, and webhooks through one governed endpoint, with every call tied to the person who signed in.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
42 tools
How to connect
How to connect Mailtrap to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Mailtrap once
-
Open Connections, choose Add connection, and pick Mailtrap.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Mailtrap API key. One person generates a token in Mailtrap and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Mailtrap MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Mailtrap MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Mailtrap MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Mailtrap to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Mailtrap through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Find out why an email never arrived
Ask for the email logs for a customer's address, see whether the message bounced or was rejected, and check whether the address landed on the suppression list, all before replying to the ticket.
-
Marketing
Check deliverability by mailbox provider
Pull Mailtrap stats broken down by email service provider and by date to see whether Gmail or Outlook deliveries dipped last week and whether a campaign was affected.
-
Engineering
Set up a new sending domain
Add a domain in Mailtrap, generate the setup instructions to hand to whoever manages DNS, and confirm the domain shows as ready once the records are in place.
-
Operations
Clear an address suppressed by mistake
Search the suppression list for a customer who says they stopped receiving mail, and remove the entry so the next message goes out.
-
Product
Compare performance across email categories
Ask how password resets, receipts, and onboarding emails performed this month, using Mailtrap stats by category, and spot which stream needs attention.
-
IT
Review webhooks after an incident
List every Mailtrap webhook, check which endpoint each one points to, and update the ones that moved during a migration so bounce and delivery events keep flowing.
Try asking
- “List every Mailtrap domain and its verification status.”
- “Show sending stats by Mailtrap domain this week.”
- “Add this bouncing address to Mailtrap suppressions.”
Compare
Elaichi vs Zapier MCP vs Composio for Mailtrap
All three can connect Mailtrap to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Mailtrap tools | Allow or restrict single Mailtrap tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Mailtrap call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Mailtrap tools for your AI agents
42 tools are ready to call through Elaichi's MCP endpoint the moment you connect Mailtrap, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Mailtrap gets you
6 screens from the product, each doing one job for your Mailtrap account.
The agent
Ask about Mailtrap domains in plain language.
Type a question, get answers from live Mailtrap domains, suppressions and stats.
- domains
- suppressions
- stats
- company infos
Ask Elaichi to work across your apps.
List every Mailtrap domain and its verification status.
Show sending stats by Mailtrap domain this week.
Add this bouncing address to Mailtrap suppressions.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Mailtrap.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
42 Mailtrap tools land ready to call.
Domains, company infos, suppressions and stats are covered without custom code.
- List all Mailtrap domains
- Create a Mailtrap domain
- Get single Mailtrap domain by ID
- Update a Mailtrap domain by ID
ElaichiToolsToolboxes
Each team gets its own Mailtrap toolbox.
Curate one toolbox per team and scope it to the work they do.
- Product engineering
- Marketing
- Lifecycle
- Support
ElaichiToolboxesShared connections
Share a Mailtrap account, not a credential.
Teammates send through a connection while the API token stays with its owner.
- Marketing
- Product engineering
- Support
- Lifecycle EMEA
ElaichiConnectionsAudit log
Every Mailtrap call is on the record.
When, who, what happened, type and resource for each domain and suppression call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your Mailtrap digest.
Six steps fetch stats, group them, draft a digest and wait for approval.
Mailtrap digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch domains
Mailtrap
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Mailtrap
Queued
Collections and dashboards
Mailtrap delivery numbers arrive already computed.
Four metrics, 14 days of sending stats and a team breakdown, refreshed on schedule.
Mailtrap health
Refreshed 4 minutes ago · every 15 minutes · from the domains collection
Domains
1,284 ↓ 12%
Suppressions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Domains created
Last 14 days
By team
Share of activity
Marketing 34%
Product engineering 27%
Support 21%
Lifecycle EMEA 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Mailtrap to Claude?
Two steps. In Elaichi, choose Mailtrap and paste in a Mailtrap API key, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and the whole thing takes a few minutes.
Does Mailtrap work with ChatGPT and Cursor as well as Claude?
Yes. Once Mailtrap is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Mailtrap once and every client uses it.
What can an AI agent actually do with my Mailtrap data?
It can look up Mailtrap email logs for a given message or recipient, pull sending stats by domain, category, mailbox provider, or date, and check or clear entries on the suppression list. It can also add and update sending domains, generate the setup instructions for them, and manage the webhooks that send delivery events to other systems. Mailtrap has a lot of ground to cover, so short concrete asks such as "show bounces for this address since Monday" get better results than long paragraphs.
Does connecting Mailtrap give the AI access to every account and domain?
No. The AI works inside the access of the Mailtrap API key the person connected with, so it sees the accounts, domains, and logs that key can see and nothing more. Elaichi can narrow that further by hiding actions or resources for a team, and it can never grant anything the key itself does not allow.
Can I stop an agent from deleting or changing things in Mailtrap?
Yes. In Elaichi you can block individual actions for Mailtrap, such as deleting a domain, removing a webhook, or clearing a suppression, while leaving reads on. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to a Mailtrap connection when someone leaves?
Offboarding that person in Elaichi ends their access to Mailtrap through every client at once, and their past actions stay in the audit log. A shared Mailtrap connection keeps working for everyone else on the team. If you ever want Mailtrap gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.
Does the Mailtrap MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Mailtrap is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Mailtrap?
Yes. Both let Claude, ChatGPT or Cursor use Mailtrap. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Mailtrap call.
How is Elaichi different from Composio for Mailtrap?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Mailtrap: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Mailtrap in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.