X402 API vs MisarMail MCP Server
A side-by-side look at the X402 API and MisarMail MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose X402 API for marketing work as a local process; choose MisarMail MCP Server for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose X402 API when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
Choose MisarMail MCP Server when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MISARMAIL_API_KEY, MISARMAIL_BASE_URL. - You want tools like
send_email, list_emails, get_email.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 33/100 · Emerging | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | MISARMAIL_API_KEYMISARMAIL_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 58 |
| Full listing | View X402 API | View MisarMail MCP Server |
Tools & capabilities
X402 API tools
No tool names declared yet. Check the project README from the listing page.
MisarMail MCP Server tools 58
send_emailSend a transactional email from a verified MisarMail account. `from.email` must match an email account you have already verified — use list_domains to check which sender domains are available. Returns the message ID and queue status.list_emailsList emails from a mailbox folder with optional full-text search across subject and body. Use this for reading the unified inbox; use list_campaigns for marketing sends.get_emailRead the full content of a single email by ID, including headers, body, and attachments metadata. Side effect: marks the email as read.reply_to_emailReply to an existing email thread. The sender address and threading headers are derived from the original message, so only the body is required.archive_emailMove an email to the archive folder. Reversible — the message is not deleted.validate_emailValidate an email address before sending: syntax, MX records, disposable-domain and role-account detection. Use this to protect sender reputation on imported lists.list_campaignsList email marketing campaigns with their status, audience size, and headline metrics. Filter by status to find drafts ready to send or campaigns still sending.get_campaignGet full details for one campaign: content, audience segment, schedule, and delivery statistics (sent, opened, clicked, bounced, complained).create_campaignCreate a new email marketing campaign as a draft. Creating never sends or schedules anything — once the content and audience are confirmed, call send_campaign to send it now or schedule it for later.send_campaignSend a campaign now, or schedule it for a future time by passing scheduled_at. This delivers real email to real recipients and cannot be undone once sending starts — confirm the audience with get_campaign first.list_contactsList contacts with their subscription status and engagement metrics. Filter by status to find unsubscribed or bounced addresses that should be excluded from sends.create_contactAdd a single contact. Adding a contact records consent to email them — only add addresses that opted in, or the send will damage sender reputation and may breach CAN-SPAM/GDPR.- +46 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
X402 API
{
"mcpServers": {
"x402-api-2": {
"command": "uvx",
"args": [
"x402"
]
}
}
}
MisarMail MCP Server
{
"mcpServers": {
"misarmail-mcp-server": {
"command": "npx",
"args": [
"-y",
"@misarmail/mcp@latest"
],
"env": {
"MISARMAIL_API_KEY": "YOUR_MISARMAIL_API_KEY_HERE",
"MISARMAIL_BASE_URL": "YOUR_MISARMAIL_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
X402 API is categorized under Marketing and uses a local stdio subprocess. MisarMail MCP Server belongs to Marketing and uses a local stdio subprocess. Pick X402 API for marketing work and MisarMail MCP Server for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
X402 API has no declared pricing — check the project's own site. MisarMail MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add x402-api-2 and misarmail-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, X402 API has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. MisarMail MCP Server has 61/100 (Good) with 1 views, 0 installs and 1 GitHub stars.