How do AI agents use Postmark through Open Connector?

Your user connects Postmark once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Postmark tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Postmark MCP server?

Yes. Open Connector can serve Postmark as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Postmark actions with credentials injected server-side.

Where do Postmark credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Postmark integration

Postmark integration for AI agents.

Postmark integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Postmark tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Postmark actions, managed and audited.

Your user connects Postmark once; your agent can then send transactional and marketing emails and get them to the inbox on time, every time. Postmark is a fast and reliable email delivery service for developers — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Postmark access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Postmark tools.

23 tools are generated from the published Postmark catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 23 tools. All published catalog entries are included in this page's server-rendered HTML.

Create a Domain: Create a Domain; Domains API
Create a Sender Signature: Create a Sender Signature; Sender Signatures API
Create a Server: Create a Server; Server Management API
Delete a Domain: Delete a Domain; Domains API
Delete a Sender Signature: Delete a Sender Signature; Sender Signatures API
Delete a Server: Delete a Server; Server Management API
Update a Domain: Update a Domain; Domains API
Update a Sender Signature: Update a Sender Signature; Sender Signatures API
Edit a Server: Edit a Server; Server Management API
Get a Domain: Get a Domain; Domains API
Get a Sender Signature: Get a Sender Signature; Sender Signatures API
Get a Server: Get a Server; Server Management API
List Domains: List Domains; Domains API
List Sender Signatures: List Sender Signatures; Sender Signatures API
List servers: List servers; Server Management API
Push templates from one server to another: Push templates from one server to another; Templates API
Request DNS Verification for DKIM: Request DNS Verification for DKIM; Domains API
Request a new DKIM Key: Requests a new DKIM key to be created. Until the DNS entries are confirmed, the new values will be in the `DKIMPendingHost` and `DKIMPendingTextValue` fields. After the new DKIM value is verified in DNS, the pending values will migrate to `DKIMTextValue` and `DKIMPendingTextValue` and Postmark will begin to sign emails with the new DKIM key.; Sender Signatures API
Request DNS Verification for Return-Path: Request DNS Verification for Return-Path; Domains API
Request DNS Verification for SPF: Request DNS Verification for SPF; Domains API
Request DNS Verification for SPF: Request DNS Verification for SPF; Sender Signatures API
Resend Signature Confirmation Email: Resend Signature Confirmation Email; Sender Signatures API
Rotate DKIM Key: Creates a new DKIM key to replace your current key. Until the DNS entries are confirmed, the new values will be in the `DKIMPendingHost` and `DKIMPendingTextValue` fields. After the new DKIM value is verified in DNS, the pending values will migrate to `DKIMTextValue` and `DKIMPendingTextValue` and Postmark will begin to sign emails with the new DKIM key.; Domains API

FAQ

Postmark integration, answered

How do AI agents use Postmark through Open Connector?: Your user connects Postmark once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Postmark tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Postmark MCP server?: Yes. Open Connector can serve Postmark as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Postmark actions with credentials injected server-side.
Where do Postmark credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Postmark — keep the keys.

Open source, self-hostable, with Postmark credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →