Gotify RMCP

What Gotify RMCP MCP server does

Gotify RMCP MCP server provides an MCP and command-line interface over an existing Gotify deployment. It does not replace Gotify or maintain a separate notification store. Gotify remains responsible for notification storage, delivery, users, token issuance, and application or client state.

The MCP interface exposes one tool named gotify. An agent selects the requested operation with an action argument. Available read operations include health, version, current-user details, messages, applications, clients, and runtime status. Write operations can send push notifications, create or update applications, and create clients. Deleting messages, applications, clients, or all messages is restricted by an explicit destructive confirmation.

How it works

The project supports three runtime surfaces: local MCP over stdio, Streamable HTTP MCP, and direct CLI commands. The npm package downloads the matching rgotify binary during installation. For local MCP clients, run the package with the mcp subcommand. For an HTTP deployment, run serve; the example loopback configuration listens on port 40020 and exposes /mcp.

Gotify RMCP MCP server sends requests to the configured Gotify upstream rather than implementing the Gotify REST API itself. It also provides prompts for send_notification and check_status, plus a gotify://schema/mcp-tool resource containing the current tool schema.

Setup and configuration

Set GOTIFY_URL to the address of the Gotify instance. A Gotify client token is used for reads and management operations, while an app token is used to send notifications. The README recommends creating these tokens in the Gotify web interface before using those operations.

A basic health check can be run with:

export GOTIFY_URL=https://gotify.example.com
npx -y @dinglebear/rgotify health --json

Start stdio MCP with npx -y @dinglebear/rgotify mcp, or start HTTP MCP with GOTIFY_MCP_HOST=127.0.0.1 npx -y @dinglebear/rgotify serve. HTTP deployments can use loopback development mode, static bearer tokens, or Google OAuth through lab-auth. Keep Gotify tokens and other secrets out of MCP tool arguments.

Tools and capabilities

The gotify tool supports these documented operations:

• Check health, version, authenticated user, and runtime status.
• List messages, optionally filtered by application, limit, or starting point.
• List applications and clients.
• Send a notification with message, title, priority, and extras.
• Create or update applications and create clients.
• Delete supported resources only with explicit confirmation.

The CLI provides equivalent scriptable access for health checks, serving MCP, setup, and other documented commands.

Limitations and notes

Gotify RMCP MCP server is an upstream-client layer, not a replacement for the Gotify service. It does not provide independent persistence, notification scheduling, generic webhook routing, multi-tenant isolation, or credential brokerage. The repository also does not ship a Gotify REST API or web UI.

The project supports write operations, so deployments should protect HTTP access and store credentials in environment variables, configuration files, or MCP client secret storage. Its documented scope includes Gotify management and notification actions; it should not be treated as a general-purpose reminder or messaging platform.