mcpField
N
Notify

Notify

Local
notify.cxCommunication0Updated 6d ago

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

  1. 01Send transactional and test emails
  2. 02Register or recover an account
  3. 03Add and verify sending domains
  4. 04Manage webhooks and API keys
  5. 05View email logs and usage

Use cases

  1. 01Send production transactional email from a coding agent
  2. 02Configure DNS and check domain verification
  3. 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.

mcp.json · Universal config
{
"mcpServers": {
"notifycx-notifycx": {
"command": "npx",
"args": [
"-y",
"notifycx-mcp"
],
"env": {
"NOTIFY_API_KEY": "<NOTIFY_API_KEY>"
}
}
}
}
Run commandnpx -y notifycx-mcp
Environment variables to set
NOTIFY_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.

Packages
npmnotifycx-mcp1.2.3

Tools

21

Saved tool list · updated 6d ago

ParameterTypeRequiredDescription
emailstringYesUser email for the Notify account
intentenumNosignup (default) or recover existing accountsignup | recover
acceptTermsbooleanYesMust be true — user accepts Terms and AUP

Details

From the project README

notifycx-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

ToolWhen to use
bootstrap_start / bootstrap_confirmSign up or recover without the dashboard (no API key required)
send_emailProduction transactional send (verified from)
send_test_emailNon-delivering API rehearsal
add_domainAdd domain + structured dnsRecords (type/name/value) for the user to publish at their host
check_domainPoll verification after DNS is configured
list_domains / get_domainDomain status + dnsRecords
list_webhooks / create_webhook / update_webhook / delete_webhook / get_webhook / test_webhookWebhook setup (Pro+)
list_email_logsRecent delivery logs
get_usageQuota / account_verified
list_api_keys / create_api_key / regenerate_api_key / delete_api_keyManage keys
create_billing_checkoutStripe 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

Markdown supported

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.