Claude Mailtrap connectorWhat Claude can do in your Mailtrap account.
The Claude Mailtrap connector is a desktop extension with 23 tools. 8 read logs, stats, templates, domains and test messages, 7 send emails or change templates and domains, and 8 sandbox tools stay undocumented. You need an API token and a verified domain first.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug Mailtrap into Claude
Mailtrap does two jobs for developers and product teams: it delivers real emails, and it catches test emails in a sandbox so nobody real receives them. With this extension, Claude can do both from Claude Desktop, and also tell you why a message bounced or how last month's delivery rate looked, straight from your logs and statistics.
A template checked before real people see it. send-sandbox-email sends a message to your Mailtrap test inbox, then get-sandbox-messages and show-sandbox-email-message let Claude read what arrived, HTML included. A developer can ask whether the new signup email still renders properly without leaving the chat.
A delivery problem explained. list-email-logs and get-email-log-message show the history of a sent message, its status and event trail, so Claude can tell you where a password reset got stuck.
A monthly deliverability check. get-sending-stats returns delivery, bounce, open, click and spam rates for a period, split by domain or category if you ask.
What it does not do: it runs only in Claude Desktop, eight of its sandbox tools have no description at all, and it never sends anything on a schedule or when an event happens in your app. For triggered sending, the Mailtrap Make integration runs without anyone in the chat.
Six words before you install
The terms that matter for this extension, explained once.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Desktop extension
- A connector installed and run on your own computer, inside Claude Desktop, instead of a service hosted online for every Claude app.
- Tool
- One named action a connector hands to Claude. Claude picks the ones it needs as it answers, and the directory sheet lists them all.
- Sandbox
- Mailtrap's test environment: emails sent there land in a test inbox and never reach real recipients.
- Approval
- The confirmation Claude waits for before it changes something in your account, shown in the conversation when it matters.
- MCP
- The open standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Mailtrap.
Install the Claude Mailtrap connector in three steps
- 01
Find Mailtrap in Claude Desktop
In Claude Desktop, open Customize, then Connectors, and look for Mailtrap. On a Team or Enterprise workspace, an Owner or Primary Owner has to allow it for the organization before members can install it.
- 02
Start the installation
Launch it from its line. Mailtrap says Claude Desktop then offers to configure the extension: that is where you enter your Mailtrap API token and account ID rather than signing in through a web page.
- 03
Treat the token as a password
There is no Mailtrap permission screen here: the API token you paste decides what Claude can reach. Use a token limited to what you need, and Disconnect or revoke it to cut the link.
The 23 tools of the Mailtrap extension
Mailtrap gives Claude 23 tools: 8 that read your account, 7 that change something in it, and 8 no official source describes.
Mailtrap describes fifteen of these tools in its README; the 8 sandbox project and inbox tools carry only a name. Names stay exactly as Claude shows them in the conversation.
- 8 read
- 7 write
- 8 not documented
What Claude reads (8)
8 toolsTemplates, test inbox messages, sending statistics, email logs and sending domains.
list-templates
Lists every email template in your Mailtrap account, so Claude knows which designs already exist before it talks about any of them.
get-sandbox-messages
Retrieves the list of messages that arrived in your Mailtrap test inbox.
show-sandbox-email-message
Shows one message from your test inbox in full, including its HTML and text body.
get-sending-stats
Returns delivery, bounce, open, click and spam rates for a date range, optionally broken down by domain, category, email provider or date.
list-email-logs
Lists the logs of emails already delivered or attempted, your full delivery history, with paging and filters.
get-email-log-message
Gets one sent message by its ID: a readable summary of sender, recipient, subject, time, status and engagement, then its detailed event history. It can also load the message body when Mailtrap exposes it.
list-sending-domains
Lists the domains your emails go out from, with the DNS verification status of each one.
get-sending-domain
Opens one of your email domains by its ID with its verification status and DNS records, and can include the setup instructions to follow.
What Claude sends or changes (7)
7 toolsReal and sandbox emails, templates created, updated or deleted, sending domains added or removed. No source describes a confirmation for these tools: the general rule below applies.
send-email
Approval: see the ruleSends a transactional email through Mailtrap to real recipients, either with content you write or from a Mailtrap template.
create-template
Approval: see the ruleAdds a new email template to your Mailtrap account.
update-template
Approval: see the ruleChanges an existing email template, for instance its subject line.
delete-template
Approval: see the ruleRemoves an existing email template from your account.
send-sandbox-email
Approval: see the ruleSends an email to your Mailtrap test inbox instead of real recipients, with inline content or a template.
create-sending-domain
Approval: see the ruleRegisters a new sending domain in Mailtrap. Mailtrap then expects DNS records on your side to verify it.
delete-sending-domain
Approval: see the ruleDeletes a sending domain from your Mailtrap account.
Named, not documented (8)
8 toolsThe directory lists these sandbox tools, but Mailtrap's current README does not describe them, so this page does not say what they do.
list-sandbox-projects
No official source describes this tool. The directory publishes its name, but Mailtrap's current README, which documents a larger and partly renamed set of tools, does not mention it at all, so this page does not guess.
create-sandbox-project
Its name appears on the directory sheet and nowhere in Mailtrap's documentation, so what it does is not documented by any source this page could check, and the name alone proves nothing.
delete-sandbox-project
Mailtrap's README carries no description of this name. The directory sheet lists it without any detail either, so this page does not state its effect on your account or your test data.
create-sandbox-inbox
Undocumented: neither the directory nor Mailtrap explains this tool, and its name alone is not a source. The page leaves its behaviour open.
get-sandbox-inbox
Here too the sheet gives a name and no sentence. Mailtrap's documentation does not list it, so no source describes what it returns or which inbox it looks at.
update-sandbox-inbox
Listed on the directory, absent from Mailtrap's README: no official text describes this tool, and this page does not guess its behaviour from its name, however obvious it may look.
delete-sandbox-inbox
Another sandbox name without documentation. No source says what it touches, and none describes any confirmation step specific to it.
clean-sandbox-inbox
The last of the eight undocumented sandbox tools. Mailtrap's current documentation has no entry for it, and the directory adds no description beyond the bare name, so its effect stays unknown here.
What Claude checks with you first
By default, Claude stops and asks before each action it carries out on an account for someone, right in the conversation.
No source describes a confirmation specific to the seven Mailtrap tools that send or change something, sending to real recipients included, so this default rule is what applies. On Team and Enterprise, workspace owners decide whether members may let some actions through without being asked, and they can limit what a connector does for the whole organization, for example keeping reads and closing writes. Nobody lifts that from their own account. And Claude reaches exactly what your Mailtrap API token reaches, nothing more.
Which Claude plans it runs on
None of the 819 directory sheets states availability by plan, and no official source publishes it connector by connector.
The published rule is general: desktop extensions like this one install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organization before members can use it. For the current state of the Mailtrap extension, open its sheet in the official directory.
Limits of the Claude Mailtrap connector
A connector is not an automation: Claude calls these tools while it answers you, and nothing is sent when a user signs up in your app.
Everything here comes from the directory sheet and Mailtrap's README on GitHub: neither Claude's help center nor Anthropic's developer docs cover this extension. The README now documents a much larger and partly renamed set of tools than the 23 on the sheet, and this page only counts the sheet. The verification badge is not a security audit, and Anthropic states on every sheet that it does not control a publisher's tools. Other routes sit in the Integrations hub.
Need help connecting Mailtrap to Claude?
A person reads every message.
