Notify MCP Server vs notifyd
Notify MCP Server is an MCP server published by aahl. Marketplaces we read that list it: 1 (Official MCP Registry). notifyd is an MCP server published by rmzlb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Notify MCP Server |  notifyd |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.11 Downloads/month (PyPI): 543 Downloads/week (PyPI): 119 Forks (GitHub): 8 Stars (GitHub): 28 Not marked · First seen |
Listed Version: 0.4.0 Forks (GitHub): 1 Stars (GitHub): 17 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Notify MCP Server | notifyd |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 28 (better) | 17 (worse) |
| Forks (GitHub) (differs) | 8 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-notify) | On your machine (ghcr.io/rmzlb/notifyd:0.4.0) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 12, secrets among them: 7 | 5, secrets among them: 3 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/aahl/mcp-notify | github.com/rmzlb/notifyd |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Notify MCP Server
MCP Server for notify to Weixin, Telegram, Bark, Lark, Feishu, DingTalk
notifyd
Operate a self-hosted notifyd instance: digest, jobs, retries, suppressions, projects, test sends.
How to run each
Notify MCP Server As a local MCP server: PyPI package
claude mcp add --env "DINGTALK_BOT_KEY=<YOUR_DINGTALK_BOT_KEY>" --env "FEISHU_BOT_KEY=<YOUR_FEISHU_BOT_KEY>" --env "LARK_BOT_KEY=<YOUR_LARK_BOT_KEY>" --env "PUSH_PLUS_TOKEN=<YOUR_PUSH_PLUS_TOKEN>" --env "TELEGRAM_BOT_TOKEN=<YOUR_TELEGRAM_BOT_TOKEN>" --env "WEWORK_APP_SECRET=<YOUR_WEWORK_APP_SECRET>" --env "WEWORK_BOT_KEY=<YOUR_WEWORK_BOT_KEY>" --transport stdio mcp-notify -- uvx mcp-notifyRequires: DINGTALK_BOT_KEY (secret), FEISHU_BOT_KEY (secret), LARK_BOT_KEY (secret), PUSH_PLUS_TOKEN (secret), TELEGRAM_BOT_TOKEN (secret), WEWORK_APP_SECRET (secret), WEWORK_BOT_KEY (secret)
notifyd
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: ADMIN_API_KEY (secret), DATABASE_URL (secret), JWT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Notify MCP Server asks for
DINGTALK_BOT_KEY (secret)FEISHU_BOT_KEY (secret)LARK_BOT_KEY (secret)PUSH_PLUS_TOKEN (secret)TELEGRAM_BOT_TOKEN (secret)TELEGRAM_DEFAULT_CHATTRANSPORTWEWORK_APP_AGENTIDWEWORK_APP_CORPIDWEWORK_APP_SECRET (secret)WEWORK_APP_TOUSERWEWORK_BOT_KEY (secret)
Only notifyd asks for
ADMIN_API_KEY (secret)DATABASE_URL (secret)EMAIL_FROMEMAIL_PROVIDERJWT_SECRET (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Notify MCP Server · What it can do: notifyd · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.