Ntfy Me MCP

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. The README also lists the equivalent GitHub Container Registry image, ghcr.io/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.