Mailtrap MCP integration for AI agents.

Connect AI agents to Mailtrap through 50 structured actions, including create contact export, create contact, delete contact, and clean inbox. Review authent…

ACTION CONTRACTS: 50
AUTHENTICATION: API key
SOURCE STATUS: Provider-backed

CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE

CAPABILITY PROFILE

What the Mailtrap integration exposes

The Mailtrap Agent App exposes 50 provider-backed actions for communication and developer tools work. Its current contract lets an authorized agent create a mailtrap contact export job, create a mailtrap contact, and delete a mailtrap contact. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.

A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.

For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Mailtrap account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.

VERIFIED ACTION SAMPLE

Real Mailtrap capabilities.

Showing 12 of 50 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.

create_contact_exportREAD

Create a Mailtrap contact export job.

INPUTS: accountId / filters

create_contactWRITE

Create a Mailtrap contact.

INPUTS: accountId / contact

delete_contactHIGH IMPACT

Delete a Mailtrap contact.

INPUTS: accountId / contactIdentifier

clean_inboxREVIEW

Clean all messages from a Mailtrap inbox.

INPUTS: accountId / inboxId

create_contact_eventWRITE

Create a custom event for a Mailtrap contact.

INPUTS: accountId / contactIdentifier / name / params

create_contact_fieldWRITE

Create a Mailtrap contact field.

INPUTS: accountId / name / dataType / mergeTag

create_contact_listREAD

Create a Mailtrap contact list.

INPUTS: accountId / name

create_email_templateWRITE

Create a Mailtrap email template.

INPUTS: accountId / emailTemplate

create_sending_domainWRITE

Create a Mailtrap sending domain.

INPUTS: accountId / sendingDomain

delete_contact_fieldHIGH IMPACT

Delete one Mailtrap contact field.

INPUTS: accountId / fieldId

delete_contact_listHIGH IMPACT

Delete one Mailtrap contact list.

INPUTS: accountId / listId

delete_email_templateHIGH IMPACT

Delete one Mailtrap email template.

INPUTS: accountId / emailTemplateId

INPUT CONTRACTS

Know what the action needs before it runs.

create_contact_export

accountIdOPTIONAL: Mailtrap account ID. Omit when the connection has a default account scope.
filtersOPTIONAL: Mailtrap export filters.

create_contact

accountIdOPTIONAL: Mailtrap account ID. Omit when the connection has a default account scope.
contactREQUIRED: Mailtrap contact fields for creation.

delete_contact

accountIdOPTIONAL: Mailtrap account ID. Omit when the connection has a default account scope.
contactIdentifierREQUIRED: Mailtrap contact UUID or email address. Email values are URL-encoded by the runtime.

clean_inbox

accountIdOPTIONAL: Mailtrap account ID. Omit when the connection has a default account scope.
inboxIdREQUIRED: Mailtrap inbox ID.

PROVIDER-SPECIFIC WORKFLOWS

Jobs this Agent App can support

Inspect Create Contact Export

Create a Mailtrap contact export job. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.

create_contact_export

Control Create Contact

Create a Mailtrap contact. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.

create_contact

Verify with Create Contact List

Create a Mailtrap contact list. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.

create_contact_list

SAFETY BOUNDARY

Operate Mailtrap with explicit limits

Authorize Mailtrap with API key and grant only the provider access required by the selected actions.
17 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
Treat `delete_contact`, `delete_contact_field`, and `delete_contact_list` as high-impact operations and require an explicit approval boundary.
No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Mailtrap rather than assuming unrestricted access.
After a call, inspect the structured result and execution record before reporting that the Mailtrap task completed successfully.

CONNECTION MODEL

API key

Mailtrap API token used with the Authorization Bearer header. Create or manage tokens in Mailtrap Settings > API Tokens: https://docs.mailtrap.io/email-api-smtp/setup/api-tokens/.

Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.

READ SIGNALS: 31
WRITE SIGNALS: 11
HIGH IMPACT: 6
REVIEW SIGNALS: 2

EVIDENCE AND AVAILABILITY

Provider reference

Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Mailtrap.

Official Mailtrap website

Sendbird Discord Bot MxToolbox Statuspage Mailosaur

MORE COMMUNICATION APPS CHECK LIVE AVAILABILITY