The official Postmark MCP server grew from four tools to 24; meanwhile, security coverage reported a separate npm package using the name postmark-mcp that was not affiliated with Postmark. This guide shows how to distinguish the projects, connect the official server to a coding assistant, and use its delivery tools without mistaking package names for proof of provenance.
Postmark’s official server connects an MCP-compatible assistant to the Postmark API. Its 24 tools cover sending, templates, message search, delivery diagnostics, bounces, suppressions, statistics, and webhooks. The official package is @activecampaign/postmark-mcp; the similarly named unscoped package is a different project.
We also compare a Postmark-focused transactional workflow with Volanea for teams that need campaigns and automations alongside transactional email. The distinction matters when choosing both the credentials an agent receives and the platform that owns your customer email workflows.
What is Postmark MCP?
MCP, or Model Context Protocol, lets an AI application connect to external tools through a defined interface. Postmark’s server provides that interface for a Postmark account: an assistant can call tools that work with email, templates, message records, and related account data rather than constructing raw API requests from scratch.
The official project is maintained in the ActiveCampaign/postmark-mcp GitHub repository and published under the npm scope @activecampaign. In its July 21, 2026, project update, Postmark described the server’s growth from four tools to 24 across eight categories. The categories are sending, templates, message search, delivery diagnostics, bounces, suppressions, stats, and webhooks.
The value of the server is not simply that an assistant can call an API. Some tasks involve several related records. To answer “What happened to this welcome email?”, an engineer might otherwise search for the message, inspect its events, check suppression status, and look at bounce history. A tool designed around delivery diagnosis combines those signals into an answer organized around the question.
The server supplies the tools; the assistant still interprets the request and decides which tool to call. A successful tool call also does not establish that a person saw a message. Treat provider records as evidence for debugging, then use your application logs and support process to decide what to do next.
Important security warning: verify the server before installing
The unscoped npm package named postmark-mcp is not Postmark’s official server. Postmark published a security notice about a malicious package impersonating its MCP project. Do not infer ownership from a similar package name, a search result, or a tutorial that does not lead back to the official project.
The official project is named @activecampaign/postmark-mcp, and its repository is ActiveCampaign/postmark-mcp. Start from Postmark’s project update or the GitHub repository, then follow the installation and configuration instructions there. Compare the package scope and repository identity before giving an integration access to a server token.
If the unscoped package has already been installed, use Postmark’s security notice for incident-specific guidance. Review which credentials and message data were available to the affected environment, inspect relevant account activity, and follow your organization’s credential-rotation and incident-response process.
Before an email tool reaches an AI client, use this provenance checklist:
- Confirm the exact package name:
@activecampaign/postmark-mcp. - Follow the repository link from Postmark’s official project information; do not substitute a similarly named package.
- Read the current installation instructions and compare the configured command with the official repository.
- Keep the token out of prompts, source-controlled files, shared screenshots, and chat transcripts.
- If a suspicious package was used, investigate the credential and account exposure rather than treating package removal as the whole response.
The concrete risk is supply-chain trust: an email integration can handle credentials and message content. Verify the project first, then decide what access it needs.
What can the official server do?
Postmark’s project update describes 24 tools in eight categories. That count gives a useful map of the server’s surface, but the practical distinction is between operations that inspect information and operations that change account state.
Send email and work with templates
Sending tools cover individual messages, batches, and template-based sends. Template tools include operations for listing, retrieving, creating, editing, deleting, and validating templates. These capabilities support development work such as locating the welcome template used by an application or preparing a transactional message for review.
Before a send, check the recipient, sender, subject, message body, template arguments, and message stream. Before a template change, compare the proposed edit with the current version and identify which live workflow uses it. A seemingly small edit to a shared password-reset or onboarding template can affect every application that relies on it.
Search messages and diagnose delivery
Message search and message-detail tools help find an outbound message and inspect its record. The diagnoseDelivery tool is designed to answer a broader question by combining related lookups, including message events, suppression status, and bounce history.
Postmark’s project update shows a sample diagnosis with a message marked Sent, events including Delivered, Opened×2, and Clicked, no bounce history, and this recommendation: “Email was delivered. If recipient says they didn’t see it, check their spam folder or ask them to whitelist the sender domain.” The useful detail is that the result includes a recommended next step, not just a collection of separate records. The provider-side Delivered event still does not establish which folder received the email or whether the recipient read it.
Check bounces, suppressions, statistics, and webhooks
The remaining categories cover bounce records and actions, suppression lookup and changes, delivery statistics, and webhook management. These help an engineer investigate blocked mail, review sending patterns, and manage the event notifications an application receives.
Reading a bounce record is different from changing bounce status; looking up a suppression is different from removing one. Webhook management also has meaningful input validation: the project update says webhook creation requires at least one trigger, and the server rejects non-HTTPS webhook URLs. An optional allowlist can further restrict accepted webhook domains.
How to connect it to Claude, Cursor, or another client
Use the official repository’s current setup instructions for the client you choose. Postmark documents setup for clients including Claude Desktop and Cursor, and the project’s configuration uses an npx command to run the scoped package. Client configuration locations and supported options vary, so copy the structure into the format documented for your installation rather than reusing a file from an unrelated package.
A controlled setup sequence looks like this:
- Open the official GitHub repository and confirm that the instructions refer to
@activecampaign/postmark-mcp. - Choose the Postmark server account and token the assistant should use. The token determines the Postmark context in which the server operates.
- Add the server to the client’s MCP configuration using the official command and the client’s documented configuration location.
- Supply the token and any default sender or message-stream settings through the configuration’s environment values. Store the token in an approved local secrets mechanism; do not paste it into the assistant conversation.
- Start with a read-oriented task, such as locating a known template or searching for a test message.
- For a send test, use a controlled recipient and inspect the exact message details before approving the action.
- Confirm the expected account activity and client behavior before using the connection for production work.
Postmark’s project update explains why the server uses a small HTTP client built on native fetch instead of the official Node SDK. The team wanted MCP traffic to be identifiable in Postmark logs, to centralize authentication, timeouts, and error mapping, and to reduce runtime dependencies. The update says the client also carries the MCP client’s name and version into requests and logs; operators can provide an AGENT_LABEL to distinguish multiple instances.
That rationale is useful when investigating activity: an integration that identifies its traffic makes it easier to tell agent-driven requests from other application requests. It does not change the need to review the token’s access or the actions the client allows.
Example client configuration
The following JSON illustrates the command-and-environment-variable pattern for an MCP client configuration. The environment variable names shown are POSTMARK_SERVER_TOKEN, POSTMARK_FROM_EMAIL, and POSTMARK_MESSAGE_STREAM; replace the example values with your own values and use the current repository instructions for the target client.
{
"mcpServers": {
"postmark": {
"command": "npx",
"args": ["-y", "@activecampaign/postmark-mcp"],
"env": {
"POSTMARK_SERVER_TOKEN": "your-postmark-server-token",
"POSTMARK_FROM_EMAIL": "Product Team <hello@example.com>",
"POSTMARK_MESSAGE_STREAM": "outbound"
}
}
}
}
This example shows how the server package, command, and settings fit together; the client-specific file location is not part of the JSON and differs by application. Keep real credentials in local environment configuration or your team’s secrets tooling, and exclude files containing secrets from version control. Where your client supports environment-variable substitution or a secrets manager, use that mechanism instead of writing a live token directly into a shared configuration file.
The -y option allows npx to proceed without an interactive package-install confirmation. It does not establish who published a package. The meaningful trust check is that the command names the scoped package from the official project and matches its current instructions.
Practical examples: prompts and expected results
Give the assistant a defined task, identify the relevant account object, and state what it must not change. For any operation that sends a message or changes account state, review the proposed arguments before approving the tool call.
Send a controlled transactional test
Prompt: “Send a test password-reset email to qa-inbox@example.com using the password-reset template on the outbound stream. Do not send to any other recipient. Show me the recipient, template, and stream before sending.”
The assistant can use a template-based sending tool and return the result of the Postmark operation. Before approval, confirm that the address is a controlled test inbox and that the template does not contain a live reset token or private customer data. Afterward, use the returned message information or message search to inspect the corresponding record.
Review a template change
Prompt: “Find the welcome email template used by our onboarding flow. Show the current subject and body, then validate this proposed change. Do not edit the template until I approve the exact diff.”
The expected first result is the current template content and a validation result for the proposed revision. If you approve an edit, keep it limited to the named template and fields. Review the saved result and test the onboarding flow before relying on the change in production.
Investigate a missing message
Prompt: “Diagnose the latest welcome email sent to customer@example.com. Summarize the message status, events, bounce history, and suppression status. Do not change any bounce or suppression settings.”
A diagnosis can bring these details together and provide a suggested follow-up. For example, if its output reports delivery with no bounce history, the next step may be to check the recipient’s spam folder or confirm the sender domain with the recipient. If it reports a bounce or suppression, investigate the reason before changing the account record.
The prompt’s explicit “do not change” instruction helps define the task, but a prompt alone is not an authorization system. Use client approval controls for sends and mutations, and confirm that the tool call matches the intended scope.
Security practices for AI email tools
An AI client connected to an email server can act through the credentials and tools provided to it. Keep the credential in a controlled environment, limit who can edit the MCP configuration, and review the client’s approval behavior for sends and account changes. Do not rely on a model’s interpretation of a prompt as the only barrier against a consequential action.
Separate investigation from mutation in your operating procedure. Searching for a message, reading a template, and reviewing a bounce record are different tasks from sending email, editing or deleting a template, changing a suppression, reactivating a bounce, or altering a webhook. Require a person to review the exact operation and arguments for actions that affect recipients or production configuration.
Treat retrieved email and template content as data, not instructions. A message body can contain text that attempts to influence an assistant. Such text should not authorize a send, override the user’s request, or approve a change to account state.
The project’s fetch-based client also has an operational security benefit: Postmark’s update says it was designed to make MCP traffic attributable in logs and to centralize request handling. The server carries client identity information into outbound requests and log lines, and supports an optional AGENT_LABEL for distinguishing instances. Use those records as part of investigation, alongside application logs and the actions shown in your MCP client.
For webhooks, use HTTPS endpoints and a domain allowlist where it fits your deployment. The server’s HTTPS-only validation prevents configuring a webhook with a non-HTTPS URL through that operation; it does not remove the need to validate incoming webhook requests in your application. Keep webhook secrets and verification logic on the receiving service, and test event handling before relying on it for production workflows.
Postmark’s server or a broader email platform?
Postmark’s server fits teams that want an AI assistant to work with Postmark’s transactional email and related account data. The tool surface includes sends, templates, message search, diagnostics, bounces, suppressions, statistics, and webhooks. It is a provider-specific integration, so the choice is straightforward when those are the tasks and Postmark is already the sending provider.
A different question arises when transactional messages are only one part of the requirement. If the same email system also needs campaigns, contact storage, segmentation, and automated workflows, compare those platform capabilities directly rather than treating a larger number of provider-specific MCP tools as a substitute.
| Requirement | Postmark’s official server | Volanea |
|---|---|---|
| Sending infrastructure | Postmark account and API | Amazon SES-backed sending |
| Transactional email | Tools for sending and templates | Transactional email through one API |
| Campaigns and automations | Not the focus of this Postmark MCP surface | Campaigns and automations alongside transactional email |
| MCP | 24 tools in the project update’s eight categories | 23 tools; available on every plan |
| Application interfaces | MCP tools for the Postmark API | REST API and SMTP relay |
| Contact storage | Not specified as a feature of this server | Unlimited contact storage |
We built Volanea for teams that want transactional email, campaigns, and automations together. Its REST API documentation describes 92 endpoints across sending, contacts, templates, campaigns, segments, webhooks, and suppressions. The sending endpoint processes suppression checks, contact upserts, template rendering, tracking, and delivery in one pipeline.
Some operational details matter when comparing it with a Postmark setup. Volanea uses shared Amazon SES infrastructure and does not offer dedicated IPs. Every feature ships on every plan; plans differ by monthly volume and domain count. At the monthly sending limit, sending pauses rather than generating overage billing.
Volanea includes 1,000 free emails or credits each month. Its Starter plan is $5/month for 7,500 emails, and Growth is $20/month for 50,000 emails. For development, sk_test_ keys render and log messages but do not deliver them. For SMTP, the username is volanea and the password is the project’s secret API key.
Choose Postmark when your current provider and transactional workflow are the center of the integration. Choose a broader platform when you want campaign, contact, and automation workflows in the same system as transactional sends. These are different product scopes, so compare the actual sending model, account requirements, and operational workflow your team needs.
If a unified API for transactional email, campaigns, and automations fits your stack, start free with 1,000 emails a month.
FAQ
Does the delivery diagnosis prove an email reached the inbox?
No. A Postmark Delivered event is useful provider-side evidence, and the diagnosis can include events, bounce history, and suppression status. It does not identify the recipient’s mailbox folder or prove the recipient read the message. Use the result to choose the next investigation step, such as checking spam placement or confirming the address.
Can I connect the official server to Claude or Cursor?
The ActiveCampaign repository documents configuration for Claude Desktop and Cursor, along with MCP clients that use its configuration pattern. The exact configuration location depends on the client and operating system. Start with the repository’s instructions for your client and use the scoped @activecampaign/postmark-mcp package.
What happens if my team exceeds Volanea’s monthly email volume?
Sending pauses when the monthly limit is reached; Volanea does not bill overages. Because features ship on every plan, moving to a higher-volume plan changes the monthly volume and domain allowance rather than unlocking a different feature set. Plan capacity against expected transactional and campaign traffic together.
What does 50,000 emails cost on Volanea?
Volanea Growth is $20/month for 50,000 emails. That price is for Volanea’s plan, not for the Postmark MCP package or a Postmark account. Compare the volume and domain requirements for your own workload, including both transactional messages and campaign sends, before choosing a plan.