Mailgun

🔑 BYO Key — Email

Transactional email service by Sinch. Send emails with high deliverability, tracking, and analytics.

🔑 Setup Required — Bring Your Own Key This integration requires API credentials. Store them once via setup_integration or the Dashboard Vault — they're encrypted with AES-256-GCM and never exposed.

Required Credentials

mailgun_api_key

API Key

Find your API key at app.mailgun.com → Account Settings → API Security → Private API Key

mailgun_domain

Sending Domain

Your verified sending domain (e.g. "mg.yourdomain.com"). Find it at app.mailgun.com → Sending → Domains

Get your API key at mailgun.com →

Endpoints (1)

POST send-email

Send a transactional email via Mailgun.

Field	Type	Required	Description
`from`	string	✓ Yes	Sender email address (e.g. "Name <noreply@mg.yourdomain.com>")
`to`	string	✓ Yes	Recipient email address(es), comma-separated for multiple
`subject`	string	✓ Yes	Email subject line
`html`	string	No	HTML body content
`text`	string	No	Plain text body content (fallback or alternative)
`cc`	string	No	CC recipient(s), comma-separated
`bcc`	string	No	BCC recipient(s), comma-separated
`o:tag`	string	No	Tag for tracking and analytics (e.g. "welcome-email")
`o:tracking`	string	No	Enable/disable tracking: "yes" or "no"
`attachments`	array	No	File attachments: [{ filename, content_base64 }]. content_base64 is required per item; omitting it returns 422 ATTACHMENT_MISSING_CONTENT. A mime_type key is accepted but ignored: this endpoint uses multipart mode, which posts the decoded bytes as a form-data part and carries no content type of its own — Mailgun derives it from the filename extension. Send valid base64: invalid input is currently attached as an empty file rather than rejected.

MCP Tool Names

When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:

Endpoint	MCP Tool Name
send-email	`mailgun_send_email`

← Back to all integrations