Ntfy MCP Server is an MCP server that connects large language models and autonomous agents to the ntfy push notification service, enabling devices to receive automated alerts and notifications directly from AI workflows. Software developers, system administrators, and automation engineers use it to integrate conversational clients such as Claude Desktop, Cursor, or VS Code with local or cloud-based ntfy topics. The server provides a suite of tools to publish new notifications with custom titles, priorities, emoji tags, attachments, and interactive action buttons. It also allows models to manage existing messages, dismiss or clear alerts by sequence identifier, and inspect cached topic histories without running separate scripts. Operators can configure public ntfy.sh servers or self-hosted instances using token or basic authentication, with built-in protections against server-side request forgery when overriding target hosts. In addition, user confirmation prompts ensure that critical actions like clearing messages or sending outbound calls and emails do not execute without deliberate consent, maintaining security across both STDIO and Streamable HTTP operational environments.
Category: Communication & Messaging
Tags: alerts, messaging, notifications, ntfy, push
json { "mcpServers": { "ntfy-mcp-server": { "type": "stdio", "command": "bunx", "args": ["ntfy-mcp-server@latest"], "env": { "MCP_TRANSPORT_TYPE": "stdio", "MCP_LOG_LEVEL": "info", "NTFY_DEFAULT_TOPIC": "your-topic-name" } } } } 4. Replace your-topic-name with your target ntfy topic, and optionally define NTFY_AUTH_TOKEN or NTFY_BASE_URL if utilizing a self-hosted or protected instance. 5. Save the configuration file and restart your MCP client to register the tools.Part of MCP Servers
Ntfy MCP Server allows AI clients to publish, update, clear, and poll notifications through ntfy topics. It supports message formatting with markdown, priority levels from 1 to 5, attachments, custom icons, and interactive action buttons. Clients can also search bundled emoji tags and retrieve historical message snapshots across multiple topics.
You can configure the server in your MCP client by adding it to your configuration file with the command bunx and the argument ntfy-mcp-server@latest. Specify your topic using the NTFY_DEFAULT_TOPIC environment variable. You can also run the server via Docker using ghcr.io/cyanheads/ntfy-mcp-server:latest or start it over Streamable HTTP.
Ntfy MCP Server functions with any MCP-compliant client that supports standard input/output (STDIO) or Streamable HTTP transports. Supported environments include Claude Desktop, Cursor, and VS Code. When using advanced outbound actions like email or phone calls, the client must be capable of presenting user confirmation prompts before executing requests.
Yes, Ntfy MCP Server is open-source software distributed under the Apache 2.0 license. The source code, issue tracker, and contribution guidelines are maintained publicly on GitHub in the cyanheads/ntfy-mcp-server repository. Anyone can inspect the code, contribute features, deploy self-hosted instances, or run the server across local and containerized environments.
Using the public ntfy.sh service does not require an account or credentials for standard public topics. However, if you are publishing to protected topics on ntfy.sh or a self-hosted server, you can supply a bearer access token using NTFY_AUTH_TOKEN or configure basic HTTP credentials with NTFY_AUTH_USERNAME and NTFY_AUTH_PASSWORD.