Apprise RMCP

Rust MCP server and CLI for Apprise notification fan-out across dozens of delivery backends.

Apprise RMCP is a Rust-implemented MCP server and command-line interface built on top of the Apprise notification library. Its purpose is notification fan-out: when an agent needs to send a message, Apprise handles delivery across a wide range of backend services — covering messaging platforms, email providers, push notification services, and more — without the agent needing to know the specifics of each target. The server communicates over the stdio transport, which means it runs as a subprocess and exchanges messages through standard input and output rather than a network socket. Configuration is driven by environment variables: APPRISE_URL sets the target Apprise endpoint, APPRISE_TOKEN provides authentication credentials, and APPRISE_RMCP_VERSION, APPRISE_RMCP_REPO, APPRISE_RMCP_RELEASE_BASE_URL, and RUST_LOG control versioning, repository references, release resolution, and log verbosity respectively. The package is distributed via npm under version 0.1.3 and is published by ai.dinglebear. Because no tool definitions were provided in the registry record, the specific MCP tools exposed to agents are not documented here. Agents that need to trigger multi-channel notifications — sending the same alert to Slack, email, and a push service in one call — are the primary target audience for this server.

Use cases

  • Fan out a single notification to multiple delivery backends simultaneously via Apprise
  • Trigger alerts from an AI agent workflow without managing per-service API integrations
  • Send notifications over stdio transport from within a subprocess-based MCP host
  • Configure notification targets at runtime using environment variables rather than code changes
  • Use the CLI mode to test or script Apprise notification delivery outside of an agent context

When to use it

  • When an agent needs to deliver notifications to multiple backends through a single Apprise-compatible endpoint
  • When the host environment supports stdio transport for MCP servers
  • When notification targets are managed via Apprise URLs and tokens already in use elsewhere

When not to use it

  • When a network-based transport (HTTP/SSE) is required, as this server uses stdio only
  • When the Apprise service is not already set up or accessible, since the server depends on an external Apprise endpoint
  • When specific per-tool MCP capability introspection is needed — no tool definitions are documented for this server
  • When a license-verified or audited dependency is required — no license information is available in the registry record