mcpField
F
FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe

FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe

Local
github.com/adelaidasofiaCommunication0Updated 4w ago

About FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe

paging-mcp is a FastMCP server for sending alerts through Apprise-supported notification channels. It suits on-call teams and automated systems that need multi-channel delivery, with credential redaction and channel filtering.

Key features

  1. 01Send alerts across channels
  2. 02Select configured channels
  3. 03Send to an ad-hoc channel
  4. 04Preview notifications with dry run
  5. 05Redact credentials in responses
  6. 06Report per-channel results

Use cases

  1. 01Page on-call staff about monitoring alerts
  2. 02Notify operators of batch job failures
  3. 03Send security alerts through backup channels

MCP support

Exposes Apprise-based notification tools to MCP clients, including channel listing, dry runs, and notification dispatch. Channels are configured with APPRISE_URLS, and credentials are redacted in tool responses.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
mcpbpaging-mcp.mcpb0.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

paging-mcp

License GitHub stars Last commit Open issues PyPI version PyPI downloads Built by Mycelium AI

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.

Why this exists

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:

  1. Multiple channels in parallel so a single provider outage doesn't lose the page.
  2. Channels that actually fit your operator (WhatsApp for LatAm on-calls, ntfy for self-hosters, Pushover for personal phones, Twilio SMS for the cases where it still fits).
  3. Credentials redacted in tool responses so an agent reading the output doesn't leak them back into a transcript.
  4. One MCP your agent can call from anywhere (Claude Code, Codex, Cursor, etc.) without having to ship a new MCP per channel.

Apprise solves channels 1-2 in Python. This server makes it MCP-callable with redaction and channel filtering on top.

Install

Open Claude Code, paste:

/plugin marketplace add adelaidasofia/paging-mcp
/plugin install paging-mcp@paging-mcp
Legacy install
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

Configure

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:[email protected]/[email protected]
"

Apprise URL examples by provider:

ProviderURL pattern
WhatsApp Business (Whapi)whapi+https://gate.whapi.cloud/messages/text?token=<TOKEN>&to=<+E164>
ntfyntfys://ntfy.sh/<topic>
Pushoverpover://<USER_KEY>@<APP_TOKEN>
Telegram bottgram://<BOT_TOKEN>/<CHAT_ID>
Twilio SMStwilio://<SID>:<TOKEN>@<FROM>/<TO>
Signal CLIsignal://<from>@<api-host>/<to>
Slack incoming webhookslack://<token-a>/<token-b>/<token-c>
Discord webhookdiscord://<webhook-id>/<webhook-token>
SMTP emailmailto://<user>:<pass>@<host>:<port>/?to=<dest>
AWS SNSsns://<KEY>/<SECRET>/<REGION>/<TOPIC>

Full list: https://github.com/caronc/apprise/wiki

Register with Claude Code

Project-scoped (<vault>/.mcp.json):

{
  "mcpServers": {
    "paging": {
      "command": "/Users/<you>/.claude/paging-mcp/.venv/bin/python",
      "args": ["/Users/<you>/.claude/paging-mcp/server.py"],
      "env": {
        "APPRISE_URLS": "ntfys://ntfy.sh/<your-secret-topic>"
      }
    }
  }
}

User-scoped:

claude mcp add -s user paging \
  /Users/<you>/.claude/paging-mcp/.venv/bin/python \
  /Users/<you>/.claude/paging-mcp/server.py \
  --env APPRISE_URLS="ntfys://ntfy.sh/<your-secret-topic>"

Restart Claude Code. Verify with claude mcp list.

Tools

ToolWhat it does
health_checkServer self-check + Apprise version + configured channel count.
list_configured_channelsLists the channels paging-mcp will dispatch to, credentials redacted.
notify(title, body, severity, channels?)Sends a notification to all configured channels (or a subset filter on redacted URL). Returns per-channel results.
notify_one(url, title, body, severity)Sends to a single ad-hoc Apprise URL (not persisted).
dry_run(title, body, severity)Shows what notify() would send, without dispatching.

severity is one of info, success, warning, failure. Channels that color or icon-tag use it.

Tests

.venv/bin/pip install -e ".[dev]"
.venv/bin/python -m pytest tests/ -v

16 unit + integration tests covering URL redaction, multi-channel dispatch, partial failure, channel filtering, and end-to-end paging flow with credentials in URLs.

Security notes

  • Credentials are never echoed in tool responses. Path-as-secret schemes (ntfy, pushbullet, pover) get their last path segment masked too.
  • notify_one accepts an ad-hoc URL; agents passing literal credentials are still responsible for not echoing them in conversation. Prefer APPRISE_URLS configured at server start.
  • The server does not persist channels or messages; everything is in-process.

Telemetry

This plugin sends a single anonymous install signal to myceliumai.co the first time it loads in a Claude Code session on a given machine.

What is sent:

  • Plugin name (e.g. slack-mcp)
  • Plugin version (e.g. 0.1.0)

What is NOT sent:

  • No user identifiers, names, emails, tokens, or API keys
  • No file paths, message content, or anything from your work
  • No IP address is stored after dedup processing

Why: Helps the maintainer know which plugins people actually install, so attention goes to the ones that get used.

Opt out: Set the environment variable MYCELIUM_NO_PING=1 before launching Claude Code. The hook will skip the network call entirely. Already-pinged installs leave a sentinel at ~/.mycelium/onboarded-<plugin> — delete it if you want to reset state.

License

MIT — see LICENSE.


Built by Mycelium AI. Full install or team version at diazroa.com.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.