Notify

io.github.notifycxPublished by GitHub account notifycxv1.2.3Updated Nov 5, 2026

Transactional email for coding agents: send, test, verify domains, webhooks, logs.

Overview

AI-generated overview

Notify's official MCP server lets a coding agent send transactional email, verify sending domains, manage webhooks and API keys, and check delivery logs.

What you can do
  • Send transactional email, or run a non-delivering test send before a domain is verified
  • Add, list and inspect sending domains, returning DNS records to publish and polling SPF/DKIM verification
  • List email delivery logs and check plan usage and quota
  • List, create, regenerate and delete API keys
  • Create, read, update, delete and test webhook subscriptions
  • Start signup or key recovery by email OTP and get a Stripe Checkout link for paid plans
When to use it
Useful when a coding agent should set up and operate transactional email end to end: onboarding a sending domain, sending password resets or receipts, and wiring delivery webhooks, without switching to the Notify dashboard.
Requirements
Runs locally via npx (Node.js). Needs a Notify API key in the NOTIFY_API_KEY environment variable, or none if you use the bootstrap flow to create one. Domain verification requires publishing DNS records at your DNS host; webhooks need a Pro or Scale plan.
Before you install
The API key is a secret: bootstrap_confirm and regenerate_api_key return it once, and it should go into the MCP environment rather than chat. send_email delivers real mail and counts toward quota. create_billing_checkout produces a Stripe payment link, and create_api_key, regenerate_api_key, delete_api_key and webhook changes alter account state. Domain DNS records must be published by the user.

Installation

In SourceWeft

  1. Open Notify in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

json
{  "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.

Source: mcp/README.md at commit d06abad

Tools

21

bootstrap_start

Start Notify agent signup or key recovery without the dashboard. Sends a 6-digit email OTP. No NOTIFY_API_KEY required. Ask the user to paste the code, then call bootstrap_confirm. Requires acceptTerms: true (https://notify.cx/terms).

ParametersemailrequiredintentacceptTermsrequired

bootstrap_confirm

Confirm the email OTP from bootstrap_start. Returns api_key once — instruct the user to put it in MCP env NOTIFY_API_KEY (do not leave the secret in chat). Then use add_domain / send_email. No NOTIFY_API_KEY required for this call.

ParameterscoderequiredemailrequiredintentclientHint

send_email

Send transactional email via Notify (password reset, receipt, magic link, invoice, etc.) with a verified from domain. Use when the user wants production delivery. Prefer html for the body. For non-delivering API rehearsal before domain verification, use send_test_email instead.

Parameterstorequiredfromrequiredhtmltextmessagesubjectrequired

send_test_email

API rehearsal for Notify: same request shape as production send but does not deliver and does not count toward quota. Use before domain verification or when testing the HTTP contract. For real inbox delivery, use send_email after verifying SPF/DKIM.

Parameterstorequiredfromrequiredhtmltextmessagesubjectrequired

list_domains

List Notify sending domains and verification status (SPF/DKIM). Includes structured dnsRecords (type/name/value) for the user to publish at their DNS host.

Takes no parameters.

get_domain

Get one Notify sending domain by hostname, including dnsRecords (type/name/value) and raw DNS tokens for pending verification. Show dnsRecords to the user so they can add them at their hosting provider.

Parametersdomainrequired

add_domain

Add a sending domain and start SPF/DKIM verification. Returns dnsRecords (type/name/value) the user must add at their DNS host — Notify does not publish DNS. After DNS is configured, call check_domain. Then use send_email with a from address on that domain.

ParametersdomainrequireddnsProvider

check_domain

Poll SES for domain SPF/DKIM verification status after DNS records were added. Call after add_domain. When both succeed, production send_email with that from domain is unlocked and the plan email limit lifts.

Parametersdomainrequired

list_email_logs

List recent Notify email delivery logs. Use after a send to check delivery, bounce, open, or click status.

ParameterspagelimiteventType

get_usage

Get Notify plan usage and quota (hourly/monthly sends, account_verified). Use when debugging limits or confirming production unlock.

Takes no parameters.

list_api_keys

List API key metadata for the account (id, name, prefix only — never the full secret).

Takes no parameters.

create_api_key

Create an API key (full_access required). Free plan allows one key. Prefer sending_access + domainId for app keys on Pro+.

ParametersnamerequireddomainIdpermission

regenerate_api_key

Rotate an API key secret by keyId. Returns the new api_key once — update NOTIFY_API_KEY / app secrets.

ParameterskeyIdrequired

delete_api_key

Deactivate an API key by keyId. Cannot delete the last full_access key.

ParameterskeyIdrequired

create_billing_checkout

Get a Stripe Checkout URL for Pro or Scale (full_access key). User opens the URL in a browser to pay — not the Notify dashboard.

Parametersplan

list_webhooks

List Notify webhook subscriptions (URL, events, domain scope).

Takes no parameters.

get_webhook

Get one Notify webhook by id.

Parametersidrequired

create_webhook

Create a Notify webhook for delivery events on a verified domain. Requires Pro or Scale (free plan has 0 webhooks). Use list_domains to get domainId.

ParametersdomainIdrequiredmatchModematchFromsmatchHostswebhookUrlrequiredsubscribedEventsrequired

update_webhook

Update an existing Notify webhook (URL, events, domain scope).

ParametersidrequireddomainIdmatchModematchFromsmatchHostswebhookUrlsubscribedEvents

delete_webhook

Delete a Notify webhook subscription by id.

Parametersidrequired

test_webhook

Send a test Notify webhook payload to a URL (does not require an existing subscription id).

ParametersdomainIdeventTyperequiredwebhookUrlrequired

Version history

1
  1. v1.2.3LatestNov 4, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts