ntfy-mcp
Enables sending push notifications via ntfy with a single tool, allowing Claude agents to send notifications directly without shell access.
README
ntfy-mcp
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.
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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.