Gotify MCP Server

MCP server for Gotify push notifications - send messages and manage apps/clients.

Remote serverstreamable-http

What is the Gotify MCP server?

Most developer tooling work still happens through a UI a human drives. Gotify MCP server moves it into the conversation instead. MCP server for Gotify push notifications - send messages and manage apps/clients.

The short version

MCP server and CLI for self-hosted media fleets: Sonarr, Radarr, Prowlarr, Bazarr, Tautulli, Overseerr, SABnzbd, qBittorrent, Plex, Jellyfin, and Tracearr.

  • Fleet status checks across the configured services
  • Credentialed upstream API passthrough for known service kinds
  • Table-driven OpenAPI operation metadata for Sonarr, Radarr, Prowlarr,
  • Curated commands for SABnzbd, qBittorrent, Tautulli, Bazarr, and Tracearr,
  • Code Mode over MCP for multi-step media automation scripts
  • Snippet storage and execution for repeatable Code Mode workflows

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • stdio — stdio is the preferred local MCP transport. It starts yarr mcp on demand and does not require binding a local HTTP port

What it needs from you

Configuration is passed through the environment: YARR_SERVICES, YARR_SONARR_URL, YARR_SONARR_API_KEY, RUST_LOG, YARR_MCP_TOKEN, YARR_MCP_HOST, YARR_RADARR_URL, YARR_RADARR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Gotify's toolset — stdio — is a fair guide to whether it matches your workflow. It is maintained by kcofoni; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Gotify's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
stdiostdio is the preferred local MCP transport. It starts yarr mcp on demand and does not require binding a local HTTP port.

How to install the Gotify MCP server

```json
{
  "mcpServers": {
    "yarr": {
      "url": "http://127.0.0.1:40070/mcp",
      "headers": {
        "Authorization": "Bearer ${YARR_MCP_TOKEN}"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
YARR_SERVICESConfiguration value read at startup.Optional
YARR_SONARR_URLEndpoint or connection string the server talks to.Yes
YARR_SONARR_API_KEYCredential the server authenticates with.Yes
RUST_LOGConfiguration value read at startup.Optional
YARR_MCP_TOKENCredential the server authenticates with.Yes
YARR_MCP_HOSTEndpoint or connection string the server talks to.Optional
YARR_RADARR_URLEndpoint or connection string the server talks to.Yes
YARR_RADARR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Gotify to stdio.

Frequently asked questions

It connects Gotify to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (stdio) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Gotify directly.