apprise-rmcp

MCP server and CLI for Apprise: fan out notifications to dozens of delivery backends over stdio or streamable HTTP, with auth and plugin packaging.

It exposes one MCP tool, apprise, plus the rapprise CLI. Agents can send tagged notifications through a preconfigured Apprise server, run one-off Apprise URL sends, and check upstream health through stdio MCP, Streamable HTTP MCP, or direct shell commands.

30-second path: run npx -y @dinglebear/rapprise health --json -> start loopback HTTP with APPRISE_MCP_HOST=127.0.0.1 npx -y @dinglebear/rapprise serve -> call tools/call with {"action":"health"}.

Status: operational RMCP upstream-client server. Write-capable; notification sends are intentional side effects. HTTP MCP supports loopback dev mode, static bearer tokens, and Google OAuth through lab-auth.

Not for: replacing Apprise API, storing notification destinations in this repo, scheduling reminders, building a generic webhook relay, multi-tenant isolation, or passing upstream Apprise bearer tokens through MCP tool arguments.

Contents

• Naming
• Capabilities And Boundaries
• Install
• Quickstart
• Client Configuration
• Runtime Surfaces
• MCP Tool Reference
• CLI Reference
• Configuration
• Authentication
• Safety And Trust Model
• Architecture
• Distribution Contract
• Development
• Verification
• Deployment
• Troubleshooting
• Related Servers
• Documentation
• License

Naming

Surface	This repo
Repository	apprise-rmcp
Rust crate	apprise-mcp
Binary / CLI	rapprise
npm package	@dinglebear/rapprise
npm binary aliases	apprise-rmcp, rapprise
MCP tool	apprise
Config home	~/.apprise on hosts, /data in containers
Env prefixes	APPRISE_*, APPRISE_MCP_*, APPRISE_RMCP_* for npm launcher controls

The repo and npm package use the RMCP family name, while the shipped binary uses the short Rust CLI name rapprise.

Capabilities And Boundaries

• Send notifications through tags configured in the upstream Apprise API server.
• Send one-off notifications to Apprise URL schemas with notify_url.
• Check upstream Apprise API health.
• Expose the send_alert prompt for critical alert workflows.
• Provide setup and doctor commands for local plugin/runtime checks.

This repo owns	Apprise owns	Explicitly out of scope
MCP/CLI projection, request validation, auth policy, response shaping, setup checks, and transport wiring.	Notification delivery, configured destinations, tags, delivery backend credentials, upstream API semantics.	Destination storage, scheduling, retry policy beyond upstream behavior, multi-tenant sandboxing, arbitrary webhook relay behavior.

Install

Path	Command	Best for	Notes
npm / npx	npx -y @dinglebear/rapprise --help	Linux/Windows x86_64 clients.	Verifies the release archive SHA-256 before atomic install.
Release installer	Verified installer procedure	Linux x86_64 without Node.	Verifies checksum and offline provenance before executing installer code.
Docker / Compose	docker compose up -d	Shared HTTP MCP deployments.	Reads .env and exposes container port 40050. Needs the external network first — see Deployment.
Build from source	cargo build --release	Development and audits.	Produces target/release/rapprise.
Plugin	just build-plugin && claude plugin install ./plugins/apprise	Claude Code from this checkout.	Bundled rapprise stdio plugin. Ships