FastMCP server that pages on-call via 100+ notification channels (Apprise wrapper)
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"paging": {
"env": {
"APPRISE_URLS": "ntfys://ntfy.sh/<your-secret-topic>"
},
"args": [
"/Users/<you>/.claude/paging-mcp/server.py"
],
"command": "/Users/<you>/.claude/paging-mcp/.venv/bin/python"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
FastMCP server that pages on-call via 100+ notification channels. Built on top of Apprise, which speaks WhatsApp, ntfy, Pushover, Telegram, Discord, Slack, Signal, Matrix, Gotify, mailto, Twilio SMS, AWS SNS, and dozens more.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.
MCP Security Weekly
Get CVE alerts and security updates for io.github.adelaidasofia/paging-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
FastMCP server that pages on-call via 100+ notification channels. Built on top of Apprise, which speaks WhatsApp, ntfy, Pushover, Telegram, Discord, Slack, Signal, Matrix, Gotify, mailto, Twilio SMS, AWS SNS, and dozens more.
The point is provider independence. Wire one MCP, configure as many channels as you want, get redundant paging without rewriting integration code every time you swap a vendor.
If you're building anything that needs to wake a human up — a synthetic monitor on a B2B pipeline, a long-running batch job, a security alert — you want:
Apprise solves channels 1-2 in Python. This server makes it MCP-callable with redaction and channel filtering on top.
Open Claude Code, paste:
/plugin marketplace add adelaidasofia/paging-mcp
/plugin install paging-mcp@paging-mcp
git clone https://github.com/adelaidasofia/paging-mcp ~/.claude/paging-mcp
cd ~/.claude/paging-mcp
python3 -m venv .venv
.venv/bin/pip install -r requirements.txt
Set APPRISE_URLS to one or more Apprise URLs. Newline, semicolon, or comma separated:
export APPRISE_URLS="
ntfys://ntfy.sh/<your-secret-topic>
whapi+https://gate.whapi.cloud/messages/text?token=<TOKEN>&to=+57...
pover://<USER_KEY>@<APP_TOKEN>
mailto://user:pass@smtp.example.com/?to=alerts@example.com
"
Apprise URL examples by provider:
| Provider | URL pattern |
|---|---|
| WhatsApp Business (Whapi) | whapi+https://gate.whapi.cloud/messages/text?token=<TOKEN>&to=<+E164> |
| ntfy | ntfys://ntfy.sh/<topic> |
| Pushover | pover://<USER_KEY>@<APP_TOKEN> |
| Telegram bot | tgram://<BOT_TOKEN>/<CHAT_ID> |
| Twilio SMS | twilio://<SID>:<TOKEN>@<FROM>/<TO> |
| Signal CLI | signal://<from>@<api-host>/<to> |
| Slack incoming webhook | slack://<token-a>/<token-b>/<token-c> |
| Discord webhook | discord://<webhook-id>/<webhook-token> |
| SMTP email | mailto://<user>:<pass>@<host>:<port>/?to=<dest> |
| AWS SNS | sns://<KEY>/<SECRET>/<REGION>/<TOPIC> |
Full list: https://github.com/caronc/apprise/wiki
Proj