Gotify Mcp

io.github.kcofoniPublished by GitHub account kcofoniv1.0.1Updated Oct 25, 2026

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

The publisher's own server: Cortex

Overview

AI-generated overview

A local MCP server for Gotify that lets an assistant send push notifications and manage Gotify applications, clients and messages.

What you can do
Send push messages to a Gotify server through an application token (create_message tool). Manage Gotify applications, clients and messages using a client token with the needed permissions. Connect over SSE on a configurable port or over stdio, depending on the transport setting.
When to use it
Use it when you run a self-hosted Gotify server and want an assistant to push notifications to your devices or to administer Gotify apps, clients and messages from a chat session.
Requirements
A reachable Gotify server base URL in GOTIFY_URL. A Gotify application token in GOTIFY_APP_TOKEN for sending messages, and a client token in GOTIFY_CLIENT_TOKEN with permissions to manage applications, clients and messages. Runs as a local Docker container; GOTIFY_MCP_TRANSPORT selects sse or stdio and GOTIFY_MCP_PORT sets the SSE port (default 3020).
Before you install
Two secrets are required: GOTIFY_APP_TOKEN and GOTIFY_CLIENT_TOKEN; the client token can manage applications, clients and messages, so scope it carefully. The server can send notifications and change or delete Gotify data, so actions are not read-only. Point GOTIFY_URL only at a server you trust, since tokens are sent there.

Installation

In SourceWeft

  1. Open Gotify Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Tootie integrations