Connect Postmark to Claude Code

Let Claude send templated email and manage suppressions in Postmark. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Postmark to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Postmark, you add a Postmark MCP server: a small hosted service that exposes Postmark's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Postmark account. No API keys pasted into config files.

claude mcp add --transport http postmark https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Postmark once connected?

Full read-write Postmark access lets Claude send a templated transactional message, trigger a broadcast through a message stream, add or clear an address from the suppression list, and investigate a bounce or spam complaint. The sending and list hygiene that meant hopping into the dashboard happen where you are already working.

Send a templated transactional email through a specific message stream
Trigger a broadcast send to a defined audience after you approve it
Add or remove an address from the suppression list
Reactivate a bounced or inactive recipient once it is safe to resend
Look up delivery, bounce, and open activity for a recent message
Create or update a server-side email template

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Postmark access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Postmark API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Postmark changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Postmark connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Postmark connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Postmark account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Postmark's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Postmark?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Postmark account it signs in with. Revoking access is one click in Postmark.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.