Mailgun MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILGUN_API_KEY | Yes | Your Mailgun API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 70 tools
Every tool has a clearly distinct purpose based on specific resources and actions, with no ambiguity. For example, tools differentiate between getting bounces, complaints, templates, stats, IPs, lists, and routes, each with precise paths and operations.
All tools follow a consistent verb-path naming pattern (e.g., get--v3-domain_name-bounces, post--v3-domain_name-messages, put--v3-domain_name-templates-template_name). The structure is uniform across all 70 tools, using HTTP method prefixes and versioned API paths.
With 70 tools, the count is excessive for an MCP server, making it heavy and potentially overwhelming for agents. This suggests poor scoping, as many tools could be consolidated or omitted for a more manageable interface.
The tool set provides comprehensive coverage for the Mailgun domain, including CRUD operations for emails, templates, domains, IPs, lists, routes, and analytics. It supports full lifecycle management with no apparent gaps in core functionalities.