MailPace MCP Server
OfficialThe supplied server schema exposes a single email-sending tool, so you can send transactional email with structured options.
Send an email using required
fromandtoaddresses.Optionally set
cc,bcc,replyto,subject,textbody,htmlbody,list_unsubscribe, and threading fieldsinreplyto/references.Add tags and attachments (name, content, content_type, optional cid).
The schema rejects additional properties; domain management and email-status tools from the README are not present in this schema.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MailPace MCP Server send a welcome email to newuser@example.com with subject 'Welcome!' and body 'Thanks for signing up!'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MailPace MCP (Model Context Protocol) Server
MailPace MCP Server exposes the MailPace transactional email, domain management, and email status APIs to MCP clients.
Features
Send transactional email with the Send API
List, create, update, and verify domains with the Domains API
Manage domain API tokens
Check delivery, bounce, and deferral status with the Email Status API
Optional recipient allowlist and idempotent sends
Tools expose structured output schemas and MCP behavior annotations
Related MCP server: Postmark MCP Server
Requirements
Node.js 20 or newer
A MailPace organization and domain
A domain API token to send email and check email status for that domain
An organization API token to manage domains and domain API tokens
Configuration
Credentials are read from environment variables only. They are never accepted as command-line arguments, which would expose them in process listings.
Variable | Required | Description |
| For sending and domain-scoped status | Domain API token |
| For domain management | Organization API token |
| No | Comma-separated allowlist of exact addresses or |
| No | Override the API base URL. Must be HTTPS except for localhost development. |
| No | Per-request timeout in milliseconds. Default |
| No | Retries for idempotent requests and 429 responses. Default |
At least one of MAILPACE_API_TOKEN or MAILPACE_ORGANIZATION_TOKEN is required. Tools are registered according to the available credentials.
Tools
Tool | Credential | Description |
| Domain token | Send an email. Supports attachments, tags, and |
| Domain or organization token | Get delivery, bounce, or deferral status by domain and email ID. |
| Organization token | List domains with pagination and sorting. |
| Organization token | Get a domain by ID. |
| Organization token | Create a sending domain. |
| Organization token | Update a domain's name or URL. |
| Organization token | Check DKIM and advanced verification DNS records. |
| Organization token | List a domain's API tokens. |
| Organization token | Get one domain API token. |
| Organization token | Create a domain API token. Store the returned token securely. |
| Organization token | Rename a domain API token. |
| Organization token | Revoke a domain API token. This cannot be undone. |
Sending email safely
mailpace_send_email is an external side effect. Clients and hosts should confirm recipients before invoking it. For automation, set MAILPACE_ALLOWED_RECIPIENTS to reduce the impact of mistakes or prompt injection, for example:
MAILPACE_ALLOWED_RECIPIENTS="hello@example.com,@yourcompany.com"Use an idempotency_key when retrying a send to prevent duplicate email delivery.
Client configuration
After building locally, point your MCP client at the built entry point:
{
"mcpServers": {
"mailpace": {
"command": "node",
"args": ["/absolute/path/to/mailpace-mcp/build/index.js"],
"env": {
"MAILPACE_API_TOKEN": "your-domain-api-token",
"MAILPACE_ORGANIZATION_TOKEN": "your-organization-api-token"
}
}
}
}Once published, this can also be run with npx -y @mailpace/mcp.
Build and run
npm ci
npm run build
npm startDevelopment uses tsx and TypeScript source directly:
npm run devTesting
npm testThe integration tests start the built server, connect over stdio, and exercise tool registration, request shapes, validation, error mapping, retries, and timeouts against a local mock MailPace API.
Docker
docker build -t mailpace-mcp .
docker run --rm -i \
-e MAILPACE_API_TOKEN=your-domain-api-token \
-e MAILPACE_ORGANIZATION_TOKEN=your-organization-api-token \
mailpace-mcpThe image runs as the non-root node user and installs only production dependencies.
Publishing
The package is published as @mailpace/mcp on npm and registered with the Official MCP Registry as:
com.mailpace/mailpace-mcppackage.json contains the matching mcpName field, and server.json contains the registry metadata.
One-time setup
Configure npm Trusted Publishing for
@mailpace/mcp:Open
https://www.npmjs.com/package/@mailpace/mcp/accessUnder Trusted Publisher, choose GitHub Actions
Organization or user:
mailpaceRepository:
mailpace-mcpWorkflow filename:
release.ymlAllowed action: npm publish
The release workflow authenticates to npm with GitHub OIDC, so no
NPM_TOKENsecret is used.Generate an Ed25519 key pair for DNS authentication:
openssl genpkey -algorithm Ed25519 -out key.pem PUBLIC_KEY="$(openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64)" echo "mailpace.com. IN TXT \"v=MCPv1; k=ed25519; p=${PUBLIC_KEY}\""Add the printed TXT record to
mailpace.comDNS.Add the private key as the
MCP_PRIVATE_KEYrepository secret:openssl pkey -in key.pem -noout -text | grep -A3 "priv:" | tail -n +2 | tr -d ' :\n'Do not commit
key.pem; it is gitignored.
Releasing
Update package.json and server.json to the new version, commit, then push a matching tag:
git tag v2.0.0
git push origin v2.0.0Because 2.0.0 was published before trusted publishing was enabled, use a new version such as 2.0.1 for the first workflow release. This lets npm validate the trusted publisher within its setup window. Subsequent tags publish normally with OIDC.
The Release workflow runs typechecking and tests, verifies the tag matches package.json, publishes to npm using GitHub OIDC, waits for the package to appear, and publishes the version metadata to the Official MCP Registry.
If npm publishing succeeds but the registry step fails, run the Publish MCP Registry workflow manually with the version that is already on npm.
Security
Tokens are read from the environment only.
Use a domain token for sending and an organization token only when domain management is needed.
Keep
MAILPACE_ALLOWED_RECIPIENTSset in unattended deployments.Revoke unused domain API tokens from the MailPace dashboard.
Contributing
Fork the repository.
Create a new branch for your feature or bugfix.
Commit your changes and push the branch to your fork.
Create a pull request with a detailed description of your changes.
License
This project is licensed under the MIT License. See the LICENSE file for details.
Contact
For any questions or support, please contact us at support@mailpace.com.
Available Tools
1 toolsend-emailD
Inputs: from (required), to (required), attachments, bcc, +9 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The single tool 'send-email' has a clear and distinct purpose without any ambiguity.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns. The name 'send-email' follows a verb-noun structure and stands alone without deviation.
A single tool for an email server is too minimal for the apparent scope, as email management typically involves more operations like listing, deleting, or managing templates. This feels thin and incomplete for the domain.
The tool surface is severely incomplete for an email server, covering only sending emails with no support for other essential operations like retrieving sent emails, managing contacts, or handling attachments. This will cause significant agent failures in email-related workflows.
Maintenance
Related MCP Connectors
MCP server for MailTempo's public free temporary email inboxes.
An MCP server that provides email capabilities, hosted on Alpic platform
An MCP server that provides email capabilities, hosted on Alpic platform
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceThis MCP server provides email sending functionality using Protonmail's SMTP service. It allows both Claude Desktop and Cline VSCode extension to send emails on your behalf using your Protonmail credentials.51MIT
- 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.1,712 npm64MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides email sending capabilities via SMTP, featuring tools for sending standard and template-based emails. It utilizes the FastMCP Streamable HTTP transport for flexible client connectivity over HTTP without requiring stdio subprocesses.5MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that empowers AI agents to securely send emails via SMTP, supporting plain text, HTML, and attachments.MIT