Skip to main content
Glama
TadMSTR
by TadMSTR

ntfy-mcp

Built with Claude Code CI

MCP server for sending push notifications via ntfy. One tool, no database, stateless — it's an HTTP proxy between Claude and your ntfy instance.

I added this because every automated workflow on claudebox already uses ntfy for push notifications (memory pipeline completions, backup results, resource alerts), but agents had to go through a shell-access MCP or write raw curl to send them. This gives every Claude Code session a native send_notification tool call instead.

flowchart LR
    A["Claude Code agent"] -->|"send_notification"| B["ntfy-mcp\n:8484"]
    B -->|"HTTP POST"| C["ntfy server"]
    C --> D["subscribers\nmobile · web · desktop"]

Tool

send_notification

send_notification(
    message,
    topic?,
    title?,
    priority?,
    tags?,
    markdown?,
    click?,
    icon?
)

Parameter

Type

Default

Description

message

string

required

Notification body. Supports Markdown if markdown=true.

topic

string

NTFY_DEFAULT_TOPIC

ntfy topic to publish to.

title

string

Bold title shown above the message.

priority

string

default

min | low | default | high | urgent (alias: max)

tags

list[str]

Emoji short codes or plain tags, e.g. ["white_check_mark", "claudebox"]. See the ntfy emoji list.

markdown

bool

false

Enable Markdown rendering in the notification body.

click

string

URL to open when the notification is tapped.

icon

string

URL of an icon image to display with the notification.

Returns {"ok": true, "topic": "...", "status": 200} on success, or {"ok": false, "error": "..."} on failure.

Related MCP server: ntfy-mcp

Setup

Docker

No external dependencies — the container only needs outbound HTTP access to your ntfy instance.

services:
  ntfy-mcp:
    build:
      context: /path/to/ntfy-mcp
      dockerfile: Dockerfile
    container_name: ntfy-mcp
    ports:
      - "8484:8484"
    environment:
      - NTFY_URL=https://ntfy.yourdomain.com
      - NTFY_DEFAULT_TOPIC=claudebox
      - NTFY_TOKEN=          # leave empty for open instances
      - MCP_PORT=8484
    networks:
      - claudebox-net
    restart: unless-stopped

networks:
  claudebox-net:
    external: true
cd /path/to/docker/ntfy-mcp
docker compose up -d
docker logs ntfy-mcp --tail 10

The container logs should show Uvicorn running on http://0.0.0.0:8484.

Claude Code

Add to ~/.claude/settings.json under mcpServers:

{
  "mcpServers": {
    "ntfy": {
      "type": "streamable-http",
      "url": "http://localhost:8484/mcp"
    }
  }
}

LibreChat

Add to librechat.yaml under mcpServers:

mcpServers:
  ntfy:
    type: streamable-http
    url: http://host.docker.internal:8484/mcp

Note the difference: Claude Code uses localhost; LibreChat containers reach the host via host.docker.internal.

Environment Variables

Variable

Default

Description

NTFY_URL

https://ntfy.sh

Base URL of your ntfy instance

NTFY_DEFAULT_TOPIC

claudebox

Topic used when topic is not passed to the tool

NTFY_TOKEN

(empty)

Bearer token for authenticated instances. Leave empty for open instances.

MCP_PORT

8484

Port the MCP server listens on

Copy .env.example to .env and fill in the values you need. Blank values use the defaults shown above.

Testing

pip install -r requirements.txt -r requirements-dev.txt
pytest -v

Nine tests covering header construction, priority validation, default topic fallback, HTTP error handling, and bearer token injection.

Gotchas

Topic values containing / or .. are rejected. The handler returns {"ok": false, "error": "Invalid topic: ..."} for any topic that would alter the URL path. Topics must be plain strings with no path separators.

Open vs authenticated instances. If NTFY_TOKEN is empty, no Authorization header is sent. If your ntfy instance requires auth and the token is missing or wrong, you'll get a 401 back as {"ok": false, "status": 401, "error": "..."}.

Port 8484 is the default. Adjust if you have a conflict — set MCP_PORT in the environment and update the ports binding in the compose file to match.

Standalone Value

High. If you're already running ntfy for push notifications, this is a 10-minute integration that makes every Claude agent a first-class notification sender. No dependencies, no state, nothing to maintain.

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
1Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    Enables AI agents to send push notifications to your phone through ntfy, with built-in security controls to prevent data exfiltration. It exposes a single tool notify_user for notifying when tasks complete or need attention.
    Last updated
    1
    MIT
  • A
    license
    -
    quality
    C
    maintenance
    Provides a send_notification MCP tool for push notifications to mobile devices, bypassing Claude Code's suppression of pushes when terminal has focus. Works with multiple providers like ntfy, Pushover, and Telegram.
    Last updated
    15
    MIT
  • F
    license
    A
    quality
    B
    maintenance
    Enables AI to send push notifications to your phone via a configurable gateway. It is a thin wrapper that posts to an Apprise push gateway.
    Last updated
    1

View all related MCP servers

Related MCP Connectors

  • Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.

  • Push notifications for AI agents - send instant iPhone notifications from any MCP client.

  • Create, test, publish, and manage Dreamlit notification workflows from AI clients.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TadMSTR/ntfy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server