Server data from the Official MCP Registry
Send transactional email and manage MailPace domains from MCP clients.
About
Send transactional email and manage MailPace domains from MCP clients.
Security Report
Valid MCP server (1 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
4 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: MAILPACE_API_TOKEN
Environment variable: MAILPACE_ORGANIZATION_TOKEN
Environment variable: MAILPACE_ALLOWED_RECIPIENTS
Environment variable: MAILPACE_REQUEST_TIMEOUT_MS
Environment variable: MAILPACE_MAX_RETRIES
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@mailpace/mcp@2.0.1"
],
"env": {
"MAILPACE_API_TOKEN": "your-mailpace-api-token-here",
"MAILPACE_MAX_RETRIES": "your-mailpace-max-retries-here",
"MAILPACE_ALLOWED_RECIPIENTS": "your-mailpace-allowed-recipients-here",
"MAILPACE_ORGANIZATION_TOKEN": "your-mailpace-organization-token-here",
"MAILPACE_REQUEST_TIMEOUT_MS": "your-mailpace-request-timeout-ms-here"
}
}
}
}Some servers take additional arguments. See the repository for details.
Documentation
View on GitHubFrom the project's GitHub README.
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
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 |
|---|---|---|
MAILPACE_API_TOKEN | For sending and domain-scoped status | Domain API token |
MAILPACE_ORGANIZATION_TOKEN | For domain management | Organization API token |
MAILPACE_ALLOWED_RECIPIENTS | No | Comma-separated allowlist of exact addresses or @domain rules. When set, mailpace_send_email refuses other recipients. |
MAILPACE_API_URL | No | Override the API base URL. Must be HTTPS except for localhost development. |
MAILPACE_REQUEST_TIMEOUT_MS | No | Per-request timeout in milliseconds. Default 30000. |
MAILPACE_MAX_RETRIES | No | Retries for idempotent requests and 429 responses. Default 2. |
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 |
|---|---|---|
mailpace_send_email | Domain token | Send an email. Supports attachments, tags, and Idempotency-Key. |
mailpace_get_email_status | Domain or organization token | Get delivery, bounce, or deferral status by domain and email ID. |
mailpace_list_domains | Organization token | List domains with pagination and sorting. |
mailpace_get_domain | Organization token | Get a domain by ID. |
mailpace_create_domain | Organization token | Create a sending domain. |
mailpace_update_domain | Organization token | Update a domain's name or URL. |
mailpace_verify_domain | Organization token | Check DKIM and advanced verification DNS records. |
mailpace_list_domain_api_tokens | Organization token | List a domain's API tokens. |
mailpace_get_domain_api_token | Organization token | Get one domain API token. |
mailpace_create_domain_api_token | Organization token | Create a domain API token. Store the returned token securely. |
mailpace_update_domain_api_token | Organization token | Rename a domain API token. |
mailpace_revoke_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 start
Development uses tsx and TypeScript source directly:
npm run dev
Testing
npm test
The 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-mcp
The 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-mcp
package.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/access - Under Trusted Publisher, choose GitHub Actions
- Organization or user:
mailpace - Repository:
mailpace-mcp - Workflow filename:
release.yml - Allowed action: npm publish
The release workflow authenticates to npm with GitHub OIDC, so no
NPM_TOKENsecret is used. - Open
-
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.0
Because 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.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
