About Notify
Notify’s official MCP server lets coding agents work with transactional email and account operations. It includes domain verification, delivery logs, and webhook management.
Key features
- 01Send transactional and test emails
- 02Register or recover an account
- 03Add and verify sending domains
- 04Manage webhooks and API keys
- 05View email logs and usage
Use cases
- 01Send production transactional email from a coding agent
- 02Configure DNS and check domain verification
- 03Investigate recent email delivery
MCP support
Exposes Notify tools to MCP clients for email sending, domains, webhooks, logs, and account management.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y notifycx-mcpNOTIFY_API_KEYSecretNotify API key (nk_...). Optional until bootstrap_start/bootstrap_confirm returns one.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
21Saved tool list · updated 6d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| string | Yes | User email for the Notify account | |
| intent | enum | No | signup (default) or recover existing accountsignup | recover |
| acceptTerms | boolean | Yes | Must be true — user accepts Terms and AUP |
Details
From the project READMEnotifycx-mcp
Official Model Context Protocol server for Notify.
Use this in Cursor, Claude Code, or other MCP hosts when a coding agent should call Notify tools directly. For app/CI code, prefer the notifycx SDK or plain fetch.
Install (Cursor)
Already have a key:
{
"mcpServers": {
"notify": {
"command": "npx",
"args": ["-y", "notifycx-mcp"],
"env": {
"NOTIFY_API_KEY": "nk_..."
}
}
}
}
No key yet: omit NOTIFY_API_KEY, call bootstrap_start → user pastes email OTP → bootstrap_confirm → put the returned api_key into MCP env. See agent bootstrap docs.
Never paste API key secrets into chat logs.
Tools
| Tool | When to use |
|---|---|
bootstrap_start / bootstrap_confirm | Sign up or recover without the dashboard (no API key required) |
send_email | Production transactional send (verified from) |
send_test_email | Non-delivering API rehearsal |
add_domain | Add domain + structured dnsRecords (type/name/value) for the user to publish at their host |
check_domain | Poll verification after DNS is configured |
list_domains / get_domain | Domain status + dnsRecords |
list_webhooks / create_webhook / update_webhook / delete_webhook / get_webhook / test_webhook | Webhook setup (Pro+) |
list_email_logs | Recent delivery logs |
get_usage | Quota / account_verified |
list_api_keys / create_api_key / regenerate_api_key / delete_api_key | Manage keys |
create_billing_checkout | Stripe Checkout URL for Pro/Scale |
Typical setup path: bootstrap → add_domain → user publishes dnsRecords → check_domain → send_email.
Pricing
Free: 1,000 emails/mo. Pro: $10 / 10,000. Scale: $50 / 100,000.
Publishing (maintainers)
After npm publish for notifycx-mcp, register the release with the MCP Registry: from the mcp/ directory, run mcp-publisher login github (as a notifycx org member), then mcp-publisher publish.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.