Gotify RMCP vs Notify MCP Server
Gotify RMCP is an MCP server published by dinglebear.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Notify MCP Server is an MCP server published by aahl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.3 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.1.11 Downloads/month (PyPI): 543 Downloads/week (PyPI): 103 Forks (GitHub): 8 Stars (GitHub): 29 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 | Gotify RMCP | Notify MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 29 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 8 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (gotify-rmcp) | On your machine (mcp-notify) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 2 | 12, secrets among them: 7 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/jmagar/gotify-rmcp | github.com/aahl/mcp-notify |
| 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
Gotify RMCP
Rust MCP server and CLI for Gotify push notifications and message management.
Notify MCP Server
MCP Server for notify to Weixin, Telegram, Bark, Lark, Feishu, DingTalk
How to run each
Gotify RMCP As a local MCP server: npm package
claude mcp add --env "GOTIFY_APP_TOKEN=<YOUR_GOTIFY_APP_TOKEN>" --env "GOTIFY_CLIENT_TOKEN=<YOUR_GOTIFY_CLIENT_TOKEN>" --env "GOTIFY_URL=<YOUR_GOTIFY_URL>" --transport stdio gotify-rmcp -- npx -y gotify-rmcp mcp
Requires: GOTIFY_APP_TOKEN (secret), GOTIFY_CLIENT_TOKEN (secret), GOTIFY_URL
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-notify
Requires: 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)
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 Gotify RMCP asks for
GOTIFY_APP_TOKEN (secret)GOTIFY_CLIENT_TOKEN (secret)GOTIFY_RMCP_RELEASE_BASE_URLGOTIFY_RMCP_REPOGOTIFY_RMCP_VERSIONGOTIFY_URLRUST_LOG
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)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Gotify RMCP · What it can do: Notify MCP Server · 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.