Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Transactional email for coding agents: send, test, verify domains, webhooks, logs.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
NOTIFY_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"notifycx": {
"command": "npx",
"args": [
"-y",
"notifycx-mcp"
],
"env": {
"NOTIFY_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add notifycx --env NOTIFY_API_KEY=your-value -- npx -y notifycx-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"notifycx": {
"command": "npx",
"args": [
"-y",
"notifycx-mcp"
],
"env": {
"NOTIFY_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"notifycx": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"notifycx-mcp"
],
"env": {
"NOTIFY_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account notifycx, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: NOTIFY_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.2.3) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
| 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.
Free: 1,000 emails/mo. Pro: $10 / 10,000. Scale: $50 / 100,000.
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.