Postmark MCP

Postmark MCP is the Model Context Protocol server for Postmark, the transactional email service. It gives an AI assistant direct access to the sending API and the delivery record, so composing a message, firing it through a template, and then checking whether it landed all happen in one session instead of across the dashboard and a terminal. Sending is the core action. The server can dispatch a single email with subject, HTML and plain text bodies, and a chosen message stream, or send through a stored template by passing the template alias and its merge variables. Templates themselves are readable, so an agent can list what exists and inspect the fields a template expects before filling them in. On the reporting side it reaches delivery statistics and message history: outbound sends, opens and clicks where tracking is enabled, bounces with their type and reason, and spam complaints. That makes it possible to ask why a specific recipient never received a receipt and get an answer grounded in the actual event log. It fits engineering teams who own transactional email and want an assistant that can both trigger sends during development and investigate deliverability afterward. Support and lifecycle teams use the read side alone, tracing a customer complaint back to the exact message. Server tokens in Postmark are scoped per server, which keeps a connected agent inside one sending environment.