Gotify RMCP

Rust MCP server and CLI for Gotify push notifications and message management.

Gotify RMCP is a Rust-based MCP server and CLI tool that connects AI agents to a Gotify instance for push notification delivery and message management. It communicates over the stdio transport and is distributed as an npm package at version 0.1.3.

Configuration is handled entirely through environment variables. GOTIFY_URL points the server at a running Gotify instance. GOTIFY_APP_TOKEN authenticates outbound message sending, while GOTIFY_CLIENT_TOKEN authenticates read and management operations. Additional variables — GOTIFY_RMCP_VERSION, GOTIFY_RMCP_REPO, and GOTIFY_RMCP_RELEASE_BASE_URL — control version and release metadata. RUST_LOG can be set to adjust log verbosity.

Because no tool list was published in the registry record, the exact set of agent-callable operations cannot be enumerated here. Based on the stated purpose — push notifications and message management — agents connecting to this server would be expected to send notifications to a Gotify server and interact with stored messages, but only capabilities confirmed at runtime should be relied upon.

This server is the right choice when an agent workflow needs to deliver notifications through a self-hosted Gotify deployment and the host environment supports stdio-based MCP transports. It is not a fit for cloud notification services, SMS, email, or any non-Gotify push backend.

Use cases

  • Send push notifications to a self-hosted Gotify server from an AI agent workflow
  • Manage messages stored on a Gotify instance as part of an automated pipeline
  • Integrate Gotify alerting into an MCP-based agent without writing custom API glue

When to use it

  • The target notification backend is a self-hosted Gotify server
  • The MCP host supports stdio transport
  • Both an app token and a client token for the Gotify instance are available

When not to use it

  • Notifications must go to services other than Gotify (e.g. Slack, email, SMS)
  • The MCP host requires an HTTP or SSE transport rather than stdio
  • No self-hosted Gotify instance is available
  • A full enumerated tool list is required before deployment — the registry record publishes none