
Gets domain verification details by id. Requires account token.
Generate MCP URLOverview: Gets domain verification details by id. Requires account token through Postmark.
Benefits:
Common Use Cases:
With Adopt AI, your agents can tap into Postmark's full transactional email capabilities. Here are five ways teams use the Postmark MCP integration:
1. Transactional Email Automation
AI agents trigger Postmark transactional emails based on app events like account creation, order confirmations, and shipping updates for reliable delivery.
2. Email Deliverability Monitoring & Alerting
AI agents track Postmark delivery rates, bounces, and spam complaints, alerting teams to issues and recommending actions to maintain sender reputation.
3. Template Management & Versioning
AI agents manage Postmark email templates, track version history, and ensure consistent branding and content across all transactional communications.
4. Bounce & Suppression List Management
AI agents monitor Postmark bounce data, automatically clean suppression lists, and reactivate recovered addresses to maximize deliverability.
5. Email Analytics & Performance Reporting
AI agents pull Postmark delivery, open, and click data to generate performance reports and identify opportunities to improve email engagement.

Returns server configuration and sending flags for the token’s server.

Gets webhook configuration by id including triggers and url.

Triggers return-path CNAME verification for a domain id. Requires account token.

Lists bounce tags in use for filtering and reporting on this server.

Lists email templates with TemplateType filter and pagination count/offset. Returns ids for PM_GET_TEMPLATE.

Lists open tracking events for a message id with count and offset.

Click tracking aggregate stats for a date range via /stats/outbound/clicks.

Sends up to 500 messages in one call via POST /email/batch with Messages array in _rawBody. Returns status per message. For templates use PM_SEND_BATCH_WITH_TEMPLATE.

Updates webhook with PUT _rawBody on /webhooks/{id}.

Gets full details for an outbound message id including events timeline.

Lists click tracking events for a message id with count and offset.

Deletes a domain from the account. Requires account token.

Creates a new server on the account via POST _rawBody. Requires account token.

Lists message streams (outbound, broadcast, inbound) for the server.

Gets bounce detail by bounce id. Returns diagnostic type and inactive flag.

Send volume and delivery stats for a date range via GET /stats/outbound (sent/processed series). Same endpoint family as PM_GET_OUTBOUND_STATS with emphasis on send counts.

Outbound send statistics for a date range via GET /stats/outbound. Returns sent/bounce/opens aggregate series.

Lists bounces with optional filter (Bounce types), count, and offset. Returns bounce records for remediation. Use PM_GET_BOUNCE for one id.

Returns aggregate bounce counts grouped by type for the server. Quick bounce overview without listing every record.

Gets one message stream configuration by id.

Batch send with templates using POST /email/batchWithTemplates. Supply _rawBody with Messages including TemplateId and TemplateModel.

Sends email using a server template id and TemplateModel object. Most common for transactional mail. POST /email/withTemplate with fields in _rawBody.

Deletes a webhook subscription from the server.

Lists inbound processed messages with filters and pagination. Use for support mailbox automation.

Patches message stream settings with PATCH _rawBody.

Retries inbound processing for a failed inbound message id.

Lists suppressions (blocked recipients) for the server stream with count and offset.

Creates a template via POST _rawBody (Name, Subject, HtmlBody, TextBody, Alias). Returns new template id.

Deletes a template permanently from the server.

Creates webhook via POST _rawBody (Url, Triggers, MessageStream).

Bypasses inbound rules for a message id so it can flow to next hook stage.

Sends a single email via POST /email with From, To, Subject, HtmlBody/TextBody, TrackOpens, Metadata, etc. in _rawBody. Returns MessageID and submitted envelope. Use PM_SEND_EMAIL_WITH_TEMPLATE for templates.

Creates a message stream via POST _rawBody when your plan allows.

Updates template fields with PUT on /templates/{id} using _rawBody.

Updates server-level settings with PUT _rawBody (Name, Color, TrackOpens, etc.).

Bounce breakdown stats for a date range via /stats/outbound/bounces.

Reactivates a bounce so future mail to that recipient can be attempted again after fixing the cause.

Deletes a suppression for an email on a stream via DELETE with query EmailAddress per Postmark API.

Open tracking aggregate stats for a date range via /stats/outbound/opens.

Retrieves raw SMTP dump content for a bounce id for deep debugging of remote MTA responses.

Gets template body and metadata by id or alias.

Archives a message stream by id when no longer needed.

Registers a new sender domain via POST _rawBody (Name). Requires account token.

Triggers DKIM verification poll for a domain id. Requires account token.

Creates a suppression entry via POST _rawBody for the given message stream path.

Validates and test-renders a template with POST /templates/{id}/validate using TestRenderModel in _rawBody. Use before production sends.

Spam complaint statistics for outbound mail over a date range.

Lists all servers on the Postmark account. Requires account token.

Searches outbound message history with recipient, tag, status, date range, count, and offset. Returns summaries with MessageID.

Gets inbound message detail including stripped text and attachments metadata.

Lists sender domains on the account with DKIM/return-path status. Requires account token.

Unarchives a previously archived stream.

Lists webhooks configured on the server with optional message stream filter.

Deletes a server by id from the account. Requires account token.

Returns raw RFC822 content for an outbound message id when available.
Do I need my own developer credentials to use Postmark MCP with Adopt AI?
No, you can get started immediately using Adopt AI's built-in Postmark integration. For production use, we recommend configuring your own API credentials for greater control and security.
?
Can I connect Postmark with other apps through Adopt AI?
Yes! Adopt AI supports multi-app workflows, so your AI agents can seamlessly move data between Postmark and CRMs, spreadsheets, messaging platforms, and more.
?
Is Adopt AI secure?
Absolutely. Adopt AI is SOC 2 Type 2 certified and ISO/IEC 27001 compliant, and adheres to EU GDPR, CCPA, and HIPAA standards. All data is encrypted in transit and at rest, ensuring the confidentiality, integrity, and availability of your data. Learn more here.
?
What happens if the Postmark API changes?
Adopt AI maintains and updates all integrations automatically, so your agents always work with the latest API versions, no manual maintenance required.
?
Do I need coding skills to set up the Postmark integration?
Not at all. Adopt AI's zero-shot API discovery means your agents understand Postmark's schema on first contact. Setup takes minutes with no code required.
?
How do I set up custom Postmark MCP in Adopt AI?
For a step-by-step guide on creating and configuring your own Postmark API credentials with Adopt AI, see here.