MCP is overkill for Notify

Copy a snippet. Grab an API key. Done.

Model Context Protocol is a fine idea for tools that need a protocol. Sending transactional email is one fetch with an x-api-key. Wrapping that in MCP mostly adds setup and a worse place to stash your key.

What we recommend instead

Sign up and copy your API key from Credentials.
Paste a send snippet into your app (or let your AI write it).
POST https://notify.cx/api/email/send — same logs and webhooks as any other client.

Full walkthrough: Quick start guide.

One HTTP call

This is the whole integration. No server to clone, no MCP config, no SSE tunnel.

// 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!',
    message: '<h1>Welcome!</h1><p>Thanks for joining us.</p>'
  })
});

const data = await response.json();

Skip the protocol theater

Get an API key and send your first email in minutes.

Frequently asked questions

Does Notify have an MCP server?

No — and you do not need one. Notify is a single HTTP call with an API key. Wrapping that in Model Context Protocol is overkill.

How should AI agents send email with Notify?

Have the agent (or you) copy a fetch/curl snippet, put NOTIFY_API_KEY in your environment, and POST to https://notify.cx/api/email/send. Same logs and webhooks as any other client.

Why not ship an official MCP?

Agents already write HTTP. An MCP layer mostly adds setup and a worse place to stash your API key. Use the API directly.