ntfy-me-mcp is a streamlined Model Context Protocol (MCP) server that enables AI assistants to send real-time notifications to your devices through the ntfy service. You can receive alerts when AI tasks complete, errors occur, or important milestones are reached, eliminating the need for constant monitoring.
To quickly set up the server with MCP-compatible assistants, add this to your MCP configuration:
{
"ntfy-me-mcp": {
"command": "npx",
"args": ["ntfy-me-mcp"],
"env": {
"NTFY_TOPIC": "your-topic-name"
}
}
}
Using direct token (less secure):
{
"ntfy-me-mcp": {
"command": "npx",
"args": ["ntfy-me-mcp"],
"env": {
"NTFY_TOPIC": "your-topic-name",
"NTFY_URL": "https://your-ntfy-server.com",
"NTFY_TOKEN": "your-auth-token"
}
}
}
Using VS Code inputs for secure token handling (recommended):
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "ntfy_token",
"description": "Ntfy Token",
"password": true
}
],
"servers": {
"ntfy-me-mcp": {
"command": "npx",
"args": ["ntfy-me-mcp"],
"env": {
"NTFY_TOPIC": "your-topic-name",
"NTFY_URL": "https://your-ntfy-server.com",
"NTFY_TOKEN": "${input:ntfy_token}",
"PROTECTED_TOPIC": "true"
}
}
}
}
"mcp": {
"servers": {
"ntfy-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"NTFY_TOPIC",
"-e",
"NTFY_URL",
"-e",
"NTFY_TOKEN",
"-e",
"PROTECTED_TOPIC",
"gitmotion/ntfy-me-mcp"
],
"env": {
"NTFY_TOPIC": "your-topic-name",
"NTFY_URL": "https://your-ntfy-server.com",
"NTFY_TOKEN": "${input:ntfy_token}",
"PROTECTED_TOPIC": "true"
}
}
}
}
npm install -g ntfy-me-mcp
npx ntfy-me-mcp
npx -y @smithery/cli install @gitmotion/ntfy-me-mcp --client claude
Create a .env file with the following variables:
# Required
NTFY_TOPIC=your-topic-name
# Optional - For private/protected ntfy servers
# NTFY_URL=https://ntfy.sh
# NTFY_TOKEN=your-access-token
# PROTECTED_TOPIC=false
NTFY_TOPIC setting)You can use natural language with AI assistants:
"Send me a notification when the build is complete"
"Notify me when the task is done"
"Alert me after generating the code"
| Parameter | Description | Required |
|---|---|---|
| taskTitle | The notification title | Yes |
| taskSummary | The notification body | Yes |
| priority | Message priority: min, low, default, high, max | No |
| tags | Array of notification tags (supports emoji shortcodes) | No |
| markdown | Boolean to enable markdown formatting | No |
| actions | Array of view action objects for clickable links | No |
Example:
{
taskTitle: "Code Generation Complete",
taskSummary: "Your React component has been created successfully with proper TypeScript typing.",
priority: "high",
tags: ["check", "code", "react"]
}
The server automatically detects URLs in your messages and creates clickable actions. You can also manually specify actions:
{
taskTitle: "Pull Request Review",
taskSummary: "Your code has been reviewed and is ready for final checks",
actions: [
{
action: "view",
label: "View PR",
url: "https://github.com/org/repo/pull/123"
},
{
action: "view",
label: "View Changes",
url: "https://github.com/org/repo/pull/123/files",
clear: true
}
]
}
You can use emoji shortcodes in your tags:
warning → ⚠️check → ✅rocket → 🚀tada → 🎉The server intelligently detects markdown syntax and automatically enables formatting. You can override this with the markdown parameter.
You can use natural language to request message fetching:
"Show me my recent notifications"
"Get messages from the last hour"
"Find notifications with title 'Build Complete'"
| Parameter | Description | Required |
|---|---|---|
| ntfyTopic | Topic to fetch messages from | No |
| since | How far back to retrieve messages ('10m', '1h', '1d', etc.) | No |
| messageId | Find a specific message by its ID | No |
| messageText | Find messages containing specific text | No |
| messageTitle | Find messages with specific title | No |
| priorities | Find messages with specific priority levels | No |
| tags | Find messages with specific tags | No |
Examples:
// Fetch recent messages
{
since: "30m"
}
// Filter by title and priority
{
messageTitle: "Build Complete",
priorities: "high",
since: "1d"
}
// Search different topic with tags
{
ntfyTopic: "updates",
tags: ["error", "warning"],
since: "all"
}
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "ntfy-me-mcp" '{"command":"npx","args":["ntfy-me-mcp"],"env":{"NTFY_TOPIC":"your-topic-name"}}'See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"ntfy-me-mcp": {
"command": "npx",
"args": [
"ntfy-me-mcp"
],
"env": {
"NTFY_TOPIC": "your-topic-name"
}
}
}
}To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"ntfy-me-mcp": {
"command": "npx",
"args": [
"ntfy-me-mcp"
],
"env": {
"NTFY_TOPIC": "your-topic-name"
}
}
}
}3. Restart Claude Desktop for the changes to take effect