Mailgun MCP Server
OfficialRelated Servers
Alternatives to Mailgun MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides a seamless email management interface through Claude, allowing users to search, read, and send emails directly through natural language conversations.4114MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that enables Claude Desktop to manage emails via SMTP and IMAP. Send emails, fetch unread messages, and create draft replies directly from conversations.323 npmMIT
- AlicenseCqualityBmaintenanceA Model Context Protocol server that enables AI models to send emails via simple tool calls, supporting both plain text and HTML formats with JWT authentication.16 npm15ISC
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that exposes Veil Mail API operations as tools for AI agents, enabling email sending, template management, audience management, and analytics retrieval through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude AI to interact with Gmail, supporting email sending, reading, searching, labeling, draft management, and batch operations through natural language commands.2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Gmail through natural language, providing comprehensive email management capabilities including sending, reading, organizing, searching, and managing drafts and labels.22GPL 3.0
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.