mcpdirectory.dev
9,129 servers · updated 23 Sept

Rgotify MCP server

community Active last commit 28 d
{
  "mcpServers": {
    "dinglebear-rgotify": {
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/rgotify@latest"
      ],
      "env": {
        "GOTIFY_RMCP_RELEASE_BASE_URL": "https://...",
        "GOTIFY_URL": "https://...",
        "GOTIFY_CLIENT_TOKEN": "<gotify_client_token>",
        "GOTIFY_APP_TOKEN": "<gotify_app_token>",
        "GOTIFY_MCP_TOKEN": "<gotify_mcp_token>",
        "GOTIFY_MCP_PUBLIC_URL": "https://..."
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @dinglebear/rgotifyversion 0.2.0

What it does

Exposes Gotify notification server management through MCP and CLI. Allows agents and developers to send notifications, inspect server health, list messages, and manage Gotify apps and clients via stdio MCP, HTTP MCP, or shell commands.

  • Send push notifications from an agent with message, title, priority, and custom fields.
  • List and delete messages or inspect server health and connected applications.
  • Create or manage Gotify clients and applications through MCP tool calls or CLI commands.

Tools this server exposes

ToolDoes
gotifyManages Gotify server operations including sending notifications, reading server health and messages, and managing apps and clients with destructive actions req

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.