Send, read, search, and label Gmail from an AI agent — community MCP with auto-OAuth.
gmail, email, community, google
Postmark
Send transactional email from an AI agent — verified deliverability, audit-friendly.
Quick answer
What it does
Wraps the Postmark REST API: send a transactional email, query message status, search the message stream, fetch bounce details, list servers and templates.
Best for
- Transactional email from agents
- Customer notifications
- Internal alert routing
- Bounce and complaint triage
Not for
- Marketing campaigns
- Cold outreach
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "postmark": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "POSTMARK_SERVER_TOKEN", "-e", "POSTMARK_FROM", "postmarkapp/mcp-server:latest" ], "env": { "POSTMARK_SERVER_TOKEN": "${POSTMARK_SERVER_TOKEN}", "POSTMARK_FROM": "${POSTMARK_FROM}" } } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshell# export POSTMARK_SERVER_TOKEN=changeme # export POSTMARK_FROM=agent@example.com claude mcp add postmark -- docker run --rm -i -e POSTMARK_SERVER_TOKEN -e POSTMARK_FROM postmarkapp/mcp-server:latestRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "postmark": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "POSTMARK_SERVER_TOKEN", "-e", "POSTMARK_FROM", "postmarkapp/mcp-server:latest" ], "env": { "POSTMARK_SERVER_TOKEN": "${POSTMARK_SERVER_TOKEN}", "POSTMARK_FROM": "${POSTMARK_FROM}" } } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "postmark": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "POSTMARK_SERVER_TOKEN", "-e", "POSTMARK_FROM", "postmarkapp/mcp-server:latest" ], "env": { "POSTMARK_SERVER_TOKEN": "${POSTMARK_SERVER_TOKEN}", "POSTMARK_FROM": "${POSTMARK_FROM}" } } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "postmark": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "POSTMARK_SERVER_TOKEN", "-e", "POSTMARK_FROM", "postmarkapp/mcp-server:latest" ], "env": { "POSTMARK_SERVER_TOKEN": "${POSTMARK_SERVER_TOKEN}", "POSTMARK_FROM": "${POSTMARK_FROM}" } } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "postmark": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "POSTMARK_SERVER_TOKEN", "-e", "POSTMARK_FROM", "postmarkapp/mcp-server:latest" ], "env": { "POSTMARK_SERVER_TOKEN": "${POSTMARK_SERVER_TOKEN}", "POSTMARK_FROM": "${POSTMARK_FROM}" } } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "docker", "args": [ "run", "--rm", "-i", "-e", "POSTMARK_SERVER_TOKEN", "-e", "POSTMARK_FROM", "postmarkapp/mcp-server:latest" ], "env": { "POSTMARK_SERVER_TOKEN": "${POSTMARK_SERVER_TOKEN}", "POSTMARK_FROM": "${POSTMARK_FROM}" } } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.postmark] command = "docker" args = [ "run", "--rm", "-i", "-e", "POSTMARK_SERVER_TOKEN", "-e", "POSTMARK_FROM", "postmarkapp/mcp-server:latest", ] env = { POSTMARK_SERVER_TOKEN = "${POSTMARK_SERVER_TOKEN}", POSTMARK_FROM = "${POSTMARK_FROM}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "postmark": { "command": { "path": "docker", "args": [ "run", "--rm", "-i", "-e", "POSTMARK_SERVER_TOKEN", "-e", "POSTMARK_FROM", "postmarkapp/mcp-server:latest" ] }, "env": { "POSTMARK_SERVER_TOKEN": "${POSTMARK_SERVER_TOKEN}", "POSTMARK_FROM": "${POSTMARK_FROM}" } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Apps directorynonePostmark doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.
- 2
Set required secrets
Set
POSTMARK_SERVER_TOKEN,POSTMARK_FROMin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
| Tool | Description | Args | Side effects |
|---|---|---|---|
send_email | Send a transactional email. | to: string, subject: string, body: string | Write |
send_template | Send a templated transactional email. | template_id: string, to: string, model: object | Write |
get_message | Look up a sent message by ID. | message_id: string | Read |
search_messages | Search the message stream by recipient, status, or tag. | query: object | Read |
Security & scope
- Access scope
- Read + write
- Sandbox
- Authenticates with a Postmark server token scoped to one logical send domain. The MCP exposes message-send and read-stream tools; rate-limited per token.
- Gotchas
- Server tokens can send email — treat them as production secrets and rotate on team changes.
- POSTMARK_FROM must match a verified sender signature in the Postmark account, or sends 422.
- Agent-drafted email can still hallucinate addresses — gate the send tool through a human approval step for high-blast-radius flows.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. email work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-email
Compare Postmark against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Postmark MCP vs [Resend MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/postmark - top-mcps.com listing for Resend
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Postmark MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/postmark (fetch https://top-mcps.com/mcp/postmark.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (POSTMARK_SERVER_TOKEN, POSTMARK_FROM) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Email MCPs
Other tools in the same category worth evaluating.
Compared with Postmark
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Email? See all Email MCPs →