M 
mailgun.com
Mailgun exposes four authenticated developer surfaces—a Mailgun Email HTTP API, Validate HTTP API, Inspect HTTP API, and a local Mailgun MCP server—all using a Mailgun private API key from the dashboard, sent via HTTP Basic Auth (`api` as username) for the HTTP APIs and via `MAILGUN_API_KEY` for the MCP server.
discovered 2mo ago
MCP servers1
- Mailgun MCP Serverdiscovered
REST · OpenAPI1
- Mailgun Email APIdiscovered
Credentials
Sign up or log in in the Mailgun dashboard, then open API Security / API Keys and copy or create a Private API key. The docs say guided setup in the welcome guide creates your first API key, and the quickstart points to API Keys. Use it with HTTP Basic Auth as username api and password = your private API key.
conventions · 0/7 published
- integrations.json——
- llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing