mcpdirectory.dev
9,129 servers · updated 23 Sept

Rapprise MCP server

community Active last commit 28 d
{
  "mcpServers": {
    "dinglebear-rapprise": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/rapprise@latest"
      ],
      "env": {
        "APPRISE_RMCP_RELEASE_BASE_URL": "https://...",
        "APPRISE_URL": "https://...",
        "APPRISE_TOKEN": "<apprise_token>",
        "APPRISE_MCP_TOKEN": "<apprise_mcp_token>",
        "APPRISE_MCP_PUBLIC_URL": "https://...",
        "APPRISE_MCP_GOOGLE_CLIENT_ID": "<apprise_mcp_google_client_id>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @dinglebear/rappriseversion 0.3.0

What it does

Rapprise exposes Apprise notifications as an MCP server, allowing agents to send tagged notifications through a preconfigured Apprise server, perform one-off notification sends to Apprise URL schemas, and check upstream health. It is for developers who want to integrate notification delivery into AI agent workflows.

  • Send notifications with predefined tags to an upstream Apprise API server from an agent.
  • Check the health status of an upstream Apprise API server via MCP.
  • Send one-off notifications to arbitrary Apprise URL schemas without preconfiguration.

Tools this server exposes

ToolDoes
appriseSend notifications and check upstream Apprise API health through tagged destinations or direct URL schemas.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.