Log inSubmit server
Ntfy Me MCP logo

Ntfy Me MCP

by gitmotion

Sends and fetches ntfy notifications through MCP, with self-hosted URLs, optional token auth, rich messages, and filtering.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Ntfy Me MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "gitmotion-ntfy-me-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ntfy-me-mcp"
      ],
      "env": {
        "NTFY_TOPIC": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y ntfy-me-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

gitmotion/ntfy-me-mcp MCP server lets AI assistants send and retrieve notifications through ntfy.sh or a self-hosted ntfy instance. It runs through npx or Docker, uses environment variables for the topic and server URL, and supports optional access-token authentication. Reach for it when an agent needs to notify a device about task completion, errors, or milestones, or inspect cached messages from an ntfy topic.

Use cases

  • Send task-completion alerts to a phone
  • Notify a user when an agent encounters an error
  • Fetch cached messages from an ntfy topic
  • Post milestone updates with titles and priorities

Key features

  • Send ntfy notifications
  • Fetch and filter cached messages
  • Support public and self-hosted ntfy
  • Use optional token authentication
  • Detect URLs and Markdown automatically
  • Set rich notification metadata

Tools2

What Ntfy Me MCP lets your agent do. Expand a tool for its parameters.

Self-reported~95 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

19/19 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · ntfy-me-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars76Stargazers on the source repository.
npm downloads948Package downloads in the last 30 days.
Last commit21d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed2Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Ntfy Me MCP works

What gitmotion/ntfy-me-mcp MCP server does

The gitmotion/ntfy-me-mcp MCP server connects an MCP-compatible AI client to the ntfy notification service. It can publish messages to a configured ntfy topic and retrieve cached notifications from topics. The destination may be the public ntfy.sh service or a self-hosted ntfy deployment.

Notifications can include a message, topic, title, priority, emoji tags, and other supported ntfy message details. The server also detects URLs in message content and can create view actions automatically. When message content contains Markdown, it can detect that formatting and enable Markdown handling without requiring a separate setting for each message.

This fits agent workflows where a user should receive an update without keeping the AI client open, such as completion notices, error alerts, or milestone reports.

How it works

The server exposes two MCP tools:

  • ntfy_me sends a notification through the configured ntfy service. Natural-language requests can be used to describe the notification, while structured message parameters control details such as the title, priority, tags, and content.
  • ntfy_me_fetch polls or retrieves cached notifications from configured ntfy topics. Fetching can be filtered using the tool's supported parameters.

The server communicates with ntfy using the configured service URL and topic. Authentication is optional and uses an ntfy access token when the target instance requires one. Smart URL and Markdown handling is performed as part of notification preparation.

Setup and configuration

The gitmotion/ntfy-me-mcp MCP server can be launched from npm with npx -y ntfy-me-mcp, or run from the published Docker image gitmotion/ntfy-me-mcp:latest.

Set NTFY_TOPIC to the topic the server should use. NTFY_URL selects the ntfy endpoint, with https://ntfy.sh shown in the configuration examples. Set NTFY_TOKEN when the ntfy server requires token authentication. Docker configurations pass these values into the container, while npx-based MCP configurations place them in the client's environment section.

The repository includes examples for npm, a locally built checkout, Docker, and OpenCode. The local-checkout example runs the built JavaScript entry point with Node.js; its path must be replaced with the actual build output location.

Tools and capabilities

The gitmotion/ntfy-me-mcp MCP server provides notification delivery and notification retrieval rather than general messaging-provider management. Its documented capabilities include:

  • Sending real-time notifications to phones or desktops through ntfy.
  • Fetching and filtering cached messages from ntfy topics.
  • Setting notification topics, titles, priorities, emoji tags, and detailed message text.
  • Detecting URLs and adding view actions automatically.
  • Detecting Markdown content and enabling Markdown formatting.
  • Connecting to public or self-hosted ntfy services.
  • Using an access token for protected ntfy instances.

Email notifications, customizable click URLs, and automatic image-URL handling are listed as future work in the README, so they should not be treated as current capabilities.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ntfy Me MCP

Run it with npx using `npx -y ntfy-me-mcp`, or use the published Docker image `gitmotion/ntfy-me-mcp:latest`.

Set `NTFY_TOPIC` for the notification topic. `NTFY_URL` selects the ntfy service, and `NTFY_TOKEN` is available when token authentication is required.

Yes. Configure `NTFY_URL` with the self-hosted ntfy endpoint and provide `NTFY_TOKEN` if that instance requires access-token authentication.

It documents `ntfy_me` for sending notifications and `ntfy_me_fetch` for retrieving or filtering cached notifications.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNtfy Me MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gitmotion-ntfy-me-mcp?style=directory)](https://allmcps.com/mcp/gitmotion-ntfy-me-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/gitmotion-ntfy-me-mcp"><img src="https://allmcps.com/api/badge/gitmotion-ntfy-me-mcp?style=directory" alt="Ntfy Me MCP on AllMCPs" /></a>