paging-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPRISE_URLS | Yes | One or more Apprise URLs, newline/semicolon/comma separated | |
| MYCELIUM_NO_PING | No | Set to 1 to opt out of telemetry |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Server self-check + channel inventory. |
| list_configured_channelsA | List the channels paging-mcp will dispatch to, with credentials redacted. |
| notifyA | Send a notification to all configured channels. |
| notify_oneA | Send a notification to a single ad-hoc Apprise URL (not persisted). Useful for one-off pages where the channel isn't in |
| dry_runB | Show what |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: health_check for server status, list_configured_channels for viewing channels, notify for broadcasting, notify_one for sending to a single URL, and dry_run for previewing. No overlap in functionality.
Names are consistent in using lowercase with underscores, and most follow a verb_noun pattern (list_configured_channels, notify, notify_one, dry_run). health_check is a compound noun but still clear. Minor deviation in verb usage (health_check vs. notify) keeps it from a perfect score.
With 5 tools, the server is well-scoped for a paging/notification service. Each tool addresses a necessary operation (health, listing, sending, sending to one, dry run) without redundancy or excessive count.
Covers core functionality: health check, channel listing, broadcasting, single notification, and preview. Lacks a tool to manage persistent channels or retrieve notification history, but these are minor gaps given the server's focus on dispatching notifications.