gotify-rmcp

MCP server and CLI for Gotify: send push notifications and manage messages, apps, and clients over stdio or streamable HTTP, with auth.

It exposes one MCP tool, gotify, plus the rgotify CLI. Agents can send notifications, inspect server health, list messages, and manage Gotify apps and clients through stdio MCP, Streamable HTTP MCP, or direct shell commands.

30-second path: set GOTIFY_URL, then run npx -y gotify-rmcp health --json -> start loopback HTTP with GOTIFY_MCP_HOST=127.0.0.1 npx -y gotify-rmcp serve -> call tools/call with {"action":"health"}.

Status: operational RMCP upstream-client server. Write-capable; destructive delete actions are gated by explicit confirmation. HTTP MCP supports loopback dev mode, static bearer tokens, and Google OAuth through lab-auth.

Not for: replacing Gotify, storing notifications independently, generic webhook routing, scheduling reminders, multi-tenant isolation, or passing Gotify 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	dinglebear-ai/rgotify
Rust crate (Cargo package)	gotify-mcp
Binary / CLI	rgotify
npm package	gotify-rmcp
npm binary aliases	gotify-rmcp, rgotify
MCP tool	gotify
MCP registry name	ai.dinglebear/gotify-rmcp
Config home	~/.gotify on hosts, /data in containers
Env prefixes	GOTIFY_*, GOTIFY_MCP_*, GOTIFY_RMCP_* for npm launcher controls

These names intentionally differ. The npm package and registry entry use the RMCP family name, the Cargo package is gotify-mcp, the git repo is rgotify, and the shipped binary uses the short Rust CLI name rgotify.

Capabilities And Boundaries

• Send Gotify push notifications with message, title, priority, and extras.
• Read server health, runtime status, server version, current user, messages, applications, and clients.
• Create or update applications and create clients.
• Delete messages, all messages, applications, or clients only after explicit destructive confirmation.
• Expose MCP prompts for common workflows and a resource containing the current tool schema.

This repo owns	Gotify owns	Explicitly out of scope
MCP/CLI projection, request validation, auth policy, response shaping, setup checks, destructive gates.	Notification storage, delivery, Gotify users, token issuance, app/client state, upstream API semantics.	Notification scheduling, independent persistence, arbitrary webhook relay behavior, multi-tenant sandboxing, credential brokerage.

Install

Path	Command	Best for	Notes
npm / npx	npx -y gotify-rmcp --help	Local MCP clients and quick trials.	Downloads the matching rgotify binary from GitHub Releases.
Release installer	curl -fsSL https://raw.githubusercontent.com/dinglebear-ai/rgotify/main/scripts/install.sh | bash	Host installs without Node.	Installs rgotify for the current Linux host.
Docker / Compose	docker compose up -d	Shared HTTP MCP deployments.	Reads .env and exposes container port 40020.
Build from source	cargo build --release	Development and audits.	Produces target/release/rgotify.
Plugi