Manage your entire email infrastructure from your AI coding assistant

We just shipped version 4 of something that's been quietly changing how we operate our own platform: an MCP (Model Context Protocol) server for RacterMX.

If you're not familiar, MCP is the protocol that lets AI tools (Claude, Cursor, Kiro, etc.) call external services directly. Our npm package @ractermx/mcp-server exposes the full RacterMX API as tools your AI assistant can use. Install with npx, point it at your API key, and your coding assistant becomes your email infrastructure operator.

Here's what that actually looks like in practice:

Example 1: Client onboarding in one prompt

"I'm onboarding a new client called Acme Corp. Add the domain acmecorp.com to my account, create aliases for info, support, billing, and sales — all forwarding to [team@acmecorp-internal.com](mailto:team@acmecorp-internal.com). Then set up a webhook to notify my Slack integration at https://hooks.slack.com/services/XXX/YYY/ZZZ whenever an email bounces on that domain. Finally, show me the DNS records I need to give them so they can point their MX to us."

One message. The assistant adds the domain, creates 4 aliases, configures the webhook, and returns the DNS records you hand to the client. Seven API calls, zero dashboard clicks, full audit trail.

Example 2: Security audit with auto-remediation

"Run a security audit across all my domains. For any domain scoring below 90, show me the specific findings that are dragging the score down and tell me which ones you can auto-fix. Then fix anything fixable and re-scan to confirm the scores improved."

The assistant iterates your domains, checks security posture scores, pulls findings on the underperformers, applies one-click DNS fixes (missing SPF includes, weak DMARC policies, missing CAA records), and re-triggers scans to verify. What used to be 30 minutes of clicking through domain tabs becomes a single conversational request.

Example 3: Daily morning briefing

"Give me a morning briefing: how many emails were processed in the last 24 hours, any bounces or rejections I should know about, any unread security notifications, and check if any of my domains dropped below a B grade overnight."

Run this every morning from your terminal or IDE. The assistant pulls stats, filters for anomalies, checks notifications, and scans security grades; then gives you a plain-English summary. If something's wrong, you can follow up in the same conversation: "Block that sender" or "Show me the full bounce details."

What's exposed:

The MCP server covers the full API surface, domains, aliases, shared domains, SMTP credentials, DNS records, security scans, email logs, webhooks, blocklists, notifications, alert rules, retention policies, and more. Every write operation generates a cryptographically-chained audit log entry, same as if you did it from the dashboard.

Authentication:

Uses a scoped RacterMX API key. You control exactly what the AI can do and you can give it domains:read + aliases:manage and it can create aliases but can't delete your domains. 15 discrete scopes, IP allowlisting, and expiration dates for defense in depth.

Setup:

{ "mcpServers": { "ractermx": { "command": "npx", "args": ["@ractermx/mcp-server@latest"], "env": { "RACTERMX_API_KEY": "sk_your_key_here" } } } } 

That's it. Works with any MCP-compatible client.