Best for
- Developers wanting to integrate AI workflows with mobile/desktop notifications
- AI agents that need task completion or error alerts
- Users of ntfy.sh or self-hosted ntfy instances
N
ntfy-me MCP Server
Community
MCP server for sending/fetching ntfy notifications from AI agents
GitHub source repository ↗
60FMRS · C
ntfy-me-mcp is a practical tool that lets AI agents easily send and fetch ntfy notifications. It supports public and self-hosted servers, offering rich notification features like priority, tags, and markdown. Installation is straightforward via npx or Docker. Security is addressed with token auth, though privacy on public topics is a consideration.
ntfy-me-mcp is a Model Context Protocol (MCP) server that enables AI assistants to send real-time notifications via the ntfy service (public or self-hosted with token support). It supports rich notifications with topics, titles, priorities, tags, and detailed messages, along with smart features like automatic URL detection for view actions and intelligent markdown formatting detection. The server can be quickly set up via npx or Docker.
Tools
ntfy_me
Send a notification to a specified ntfy topic with title, message, priority, tags, markdown, and actions.
ntfy_me_fetch
Fetch and filter cached messages from ntfy topics, with filters by time, ID, text, title, priority, and tags.
Setup
- Install the ntfy app on your device (https://ntfy.sh/app) or deploy your own ntfy server. 2. Add the server to your MCP client configuration using npx, Docker, or local install. 3. Set environment variables: NTFY_TOPIC (required), NTFY_URL (optional, defaults to https://ntfy.sh), and NTFY_TOKEN (optional). 4. Run with npx ntfy-me-mcp or install globally with npm install -g ntfy-me-mcp.
claude_desktop_config.json
{
"mcpServers": {
"ntfy-me-mcp": {
"command": "npx",
"args": [
"-y",
"ntfy-me-mcp"
],
"env": {
"NTFY_TOPIC": "your-ntfy-topic",
"NTFY_URL": "https://ntfy.sh",
"NTFY_TOKEN": "your-access-token"
}
}
}
}
Fit and risk
Not for
- Those who need email or image notifications (coming soon)
- Users needing complex notification workflows
- Those who require non-ntfy services
Required permissions
- Send notifications to configured ntfy topics
- Fetch messages from configured ntfy topics
- Network access to reach the ntfy server
Risks and side effects
- Notifications may be publicly readable if the topic is public and no token is used
- Potential unauthorized access if the token is leaked
- Dependence on ntfy service availability
Troubleshooting
- If you don't receive notifications, check your NTFY_TOPIC and NTFY_URL settings.
- For protected topics, ensure NTFY_TOKEN is set.
- Test connectivity: curl -d "test" ntfy.sh/your-topic.
- If using Docker, ensure environment variables are passed correctly.
Use cases
Notify on AI task completion
Fetch and filter recent notifications
Send real-time alerts to phone/desktop
Send notifications on self-hosted ntfy servers
Supported clients
Claude DesktopFull support
VS CodeFull support
OpenCodeFull support
Copilot CLIFull support
SmitheryFull support