Gotify MCP

tv.tootiePublished by tootie.tvv0.3.1Updated Oct 24, 2026

MCP server for self-hosted Gotify push notifications and message management.

The publisher's own server: Cortex

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that connects an assistant to a self-hosted Gotify server for push notifications and message management.

What you can do
  • Send push notifications through a self-hosted Gotify server using an application token.
  • Manage messages and other Gotify resources using a client token.
  • Connect to a chosen Gotify instance via a configured base URL.
  • Run either as a local stdio subprocess or as an HTTP container deployment.
When to use it
Useful when you self-host Gotify and want an assistant to push notifications to your devices or manage messages on that server, for example to alert yourself about finished tasks or important events.
Requirements
A local Python runtime with uvx to run the PyPI package, or a container deployment. A reachable Gotify server base URL in GOTIFY_URL, without a trailing slash. A Gotify application token in GOTIFY_APP_TOKEN for sending messages and a client token in GOTIFY_CLIENT_TOKEN for management operations. GOTIFY_MCP_TRANSPORT set to stdio when running as a local subprocess; the default is http.
Before you install
Requires two Gotify secrets, GOTIFY_APP_TOKEN and GOTIFY_CLIENT_TOKEN; the client token grants management operations, so treat it as sensitive. The assistant can send notifications and change data on your Gotify server, so review actions before allowing them. Messages and requests go to the Gotify server at the URL you configure, so point it only at a trusted instance.

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. v0.3.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