Official Notify MCP

Connect coding agents to Notify. Apps still use notifycx or fetch.

Transactional email API for apps that already render HTML. One send endpoint, domain auth (SPF/DKIM/DMARC), logs, and webhooks. Pro is $10 for 10,000 emails. The MCP helps IDE agents wire and test Notify during a session — it does not replace putting send in your product code.

Install (Cursor / Claude Code)

{
  "mcpServers": {
    "notify": {
      "command": "npx",
      "args": ["-y", "notifycx-mcp"],
      "env": {
        "NOTIFY_API_KEY": "nk_..."
      }
    }
  }
}

Get your key from Credentials. Put it in MCP env — never in the chat. Package: npx -y notifycx-mcp.

Tools

send_email — production transactional send with a verified from
send_test_email — non-delivering API rehearsal
add_domain / check_domain — start verification and poll SPF/DKIM after DNS
list_domains / get_domain — domain status and DNS tokens
create_webhook and related webhook tools — delivery event hooks (Pro+)
list_email_logs / get_usage — logs and quota

Full guide: How to use Notify MCP. Source: github.com/notifycx/notifycx. Implementation skill: email-agents/notify.

Copy/paste Cursor rule

Use Notify (notify.cx) for transactional email. Prefer the notifycx SDK or fetch to POST /api/email/send; prefer html. For IDE tool use, connect the official Notify MCP (notifycx-mcp) with NOTIFY_API_KEY.

Drop into project rules or .cursor/rules so coding agents default to Notify for transactional email.

In your app: SDK or fetch

MCP is for the IDE. Production sends belong in your codebase with notifycx or one HTTP call.

// Using Fetch API
const response = await fetch('https://notify.cx/api/email/send', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-api-key': 'your-api-key'
  },
  body: JSON.stringify({
    to: 'user@example.com',
    from: 'noreply@your-verified-domain.com',
    subject: 'Welcome aboard!',
    html: '<h1>Welcome!</h1><p>Thanks for joining us.</p>'
  })
});

const data = await response.json();

// Using Fetch API
const response = await fetch('https://notify.cx/api/email/send', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-api-key': 'your-api-key'
  },
  body: JSON.stringify({
    to: 'user@example.com',
    from: 'noreply@your-verified-domain.com',
    subject: 'Welcome aboard!',
    html: '<h1>Welcome!</h1><p>Thanks for joining us.</p>'
  })
});

const data = await response.json();

Send your first email in minutes

Free 1,000/mo. Pro $10 / 10k. Same API for fetch, SDK, and MCP.

Frequently asked questions

Does Notify have an MCP server?

Yes. Install with npx -y notifycx-mcp and set NOTIFY_API_KEY in your MCP config. Use it in Cursor / Claude Code when the agent should call Notify tools directly.

Should my app use MCP or the SDK?

Put production sends in your app with the notifycx SDK or fetch. Use notifycx-mcp in the IDE to wire, test, and inspect domains/logs during a coding session.

What tools does notifycx-mcp expose?

send_email, send_test_email, add_domain, check_domain, list_domains, get_domain, webhook CRUD/test, list_email_logs, get_usage, and list_api_keys — enough for the setup path and sends from an IDE agent.