mcp-postmark
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
@pipeworx/postmark
Postmark MCP — transactional email send + lookups. Free trial 100/mo, free forever for non-marketing testing.
Part of Pipeworx — an MCP gateway connecting AI agents to 1866+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Auth
Platform:
PLATFORM_POSTMARK_KEY(server token). BYO:?_apiKey=….
Related MCP server: Postmark MCP Server
Tools
send(from, to, subject?, htmlbody?, textbody?, tag?, replyto?, cc?, bcc?, headers?, trackopens?, trackLinks?, messagestream?)— send a single emailsend_batch(emails)— send up to 500 emailsdelivery_stats()— server-level delivery statsmessages_outbound(count?, offset?, recipient?, fromEmail?, tag?, status?, fromDate?, toDate?, subject?, mailboxHash?, metadata_*?)— outbound historymessage_outbound_detail(messageId)— single outbound detailmessage_outbound_dump(messageId)— raw MIME dumpbounces(count?, offset?, type?, inactive?, emailFilter?, tag?, messageID?, fromDate?, toDate?)— bouncesbounce(id)— single bouncebounce_activate(id)— re-activate a bounced addressserver()— current server info
Data source
Postmark, transactional email send + lookups.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"postmark": {
"url": "https://gateway.pipeworx.io/postmark/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/postmark/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1866+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/send \
-H 'Content-Type: application/json' \
-d '{"from":"sender@example.com","to":"recipient@example.com","subject":"Welcome to our service","htmlbody":"<html><body><p>Hello!</p></body></html>","textbody":"Hello!"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/send. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-postmark is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/postmark/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"postmark": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-postmark"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Postmark data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Send transactional email and manage domains, audiences, and broadcasts from any MCP client.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Provision domains, mailboxes, and run email sequencer campaigns via remote MCP.
The first MCP server for physical mail: send postcards and letters, manage lists and campaigns.
Related MCP Servers
AlicenseDqualityBmaintenanceAn MCP server implementation that allows sending emails over MailPace's fast transactional email API.1494 npm1MIT- AlicenseNot gradedqualityCmaintenanceAn MCP server implementation that enables sending emails via Postmark email services with features for sending plain text/HTML emails, using templates, tracking delivery statistics, and listing available templates.3,015 npm64MIT
- AlicenseNot gradedqualityDmaintenanceEnables sending emails through the Resend service API. Provides a simple email sending tool that integrates with MCP-compatible clients.MIT
- AlicenseNot gradedqualityDmaintenanceEnables sending and managing emails via Postmark, including email delivery with templates, template listing, and delivery statistics.MIT