Mailgun MCP integration for AI agents.
Connect AI agents to Mailgun through 17 structured actions, including get domain, add suppression, delete suppression, and verify domain. Review authenticati…
- ACTION CONTRACTS
- 17
- 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 Mailgun integration exposes
The Mailgun Agent App exposes 17 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent get mailgun domain details including dns records and sending state, add one mailgun suppression or allowlist record, and remove one mailgun suppression or allowlist record. 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 Mailgun account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Mailgun capabilities.
Showing 12 of 17 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_domainREADGet Mailgun domain details including DNS records and sending state.
INPUTS: domain
add_suppressionWRITEAdd one Mailgun suppression or allowlist record.
INPUTS: domain / kind / address / allowlistDomain / code
delete_suppressionHIGH IMPACTRemove one Mailgun suppression or allowlist record.
INPUTS: domain / kind / value
verify_domainREVIEWAsk Mailgun to verify DNS records for a sending domain.
INPUTS: domain
create_templateWRITECreate a Mailgun template and optionally its initial active version.
INPUTS: domain / name / description / createdBy / template
create_template_versionWRITECreate a new version for a Mailgun template.
INPUTS: domain / templateName / template / tag / comment
get_domain_tracking_settingsREADGet open, click, unsubscribe, and web scheme tracking settings for a domain.
INPUTS: domain
get_suppressionREADGet one Mailgun suppression or allowlist record.
INPUTS: domain / kind / value
get_templateREADGet metadata for one Mailgun template and optionally its active version.
INPUTS: domain / templateName / active
get_template_versionREADGet content and metadata for one Mailgun template version.
INPUTS: domain / templateName / versionName
list_domainsREADList Mailgun domains available to the current API key.
INPUTS: limit / skip / state / sort / authority
list_eventsREADList delivery, engagement, and failure events for a Mailgun domain.
INPUTS: domain / begin / end / ascending / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_domain
domainOPTIONAL- Mailgun sending domain name.
add_suppression
domainREQUIRED- Mailgun sending domain name.
kindREQUIRED- Suppression table to operate on.
addressOPTIONAL- Suppressed email address.
allowlistDomainOPTIONAL- Domain value to add to the Mailgun allowlist.
codeOPTIONAL- Bounce error code. Defaults to Mailgun's value when omitted.
delete_suppression
domainOPTIONAL- Mailgun sending domain name.
kindOPTIONAL- Suppression table to operate on.
valueOPTIONAL- Suppressed email address or allowlist entry value.
verify_domain
domainOPTIONAL- Mailgun sending domain name.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Domain
Get Mailgun domain details including DNS records and sending state. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_domainControl Add Suppression
Add one Mailgun suppression or allowlist record. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_suppressionVerify with Get Domain Tracking Settings
Get open, click, unsubscribe, and web scheme tracking settings for a domain. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_domain_tracking_settingsSAFETY BOUNDARY
Operate Mailgun with explicit limits
- Authorize Mailgun with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_suppression` 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 Mailgun rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Mailgun task completed successfully.
CONNECTION MODEL
API key
Mailgun private API key used with HTTP Basic auth as api:YOUR_API_KEY. Create or view API keys in Mailgun security settings.
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
- 10
- WRITE SIGNALS
- 5
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
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 Mailgun.