Home › Communication › ntfy
ntfy
Publish ntfy notifications, read the message cache, and manage users and topic access
Topics: Communication
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (npm 0.3.0)
npx -y @ni-c/[email protected]
Or add to your MCP client config:
{
"mcpServers": {
"ntfy-mcp": {
"command": "npx",
"args": [
"-y",
"@ni-c/[email protected]"
],
"env": {
"NTFY_URL": "<YOUR_VALUE>",
"NTFY_TOKEN": "<YOUR_VALUE>",
"NTFY_PASSWORD": "<YOUR_VALUE>"
}
}
}
}
NTFY_URLrequired — Base URL of the ntfy server, e.g. https://ntfy.example.net. There is deliberately no default.NTFY_TOKENsecret — ntfy access token (tk_...). Optional: an open instance needs no credentials. Mutually exclusive with NTFY_USERNAME/NTFY_PASSWORD.NTFY_USERNAME— Username for basic authentication. Must be set together with NTFY_PASSWORD.NTFY_PASSWORDsecret — Password for basic authentication. Must be set together with NTFY_USERNAME.NTFY_TOPICS— Comma-separated topics the server may use. The first is the default when a tool omits one, and the list restricts every read and write tool.NTFY_READ_ONLY— Set to exactly true to register only the six read tools (default: false — ntfy exists to publish)NTFY_INSECURE_TLS— Set to true to accept a self-signed certificate from the ntfy server (default: false)NTFY_ALLOW_TOOLS— Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)NTFY_DENY_TOOLS— Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
Package (oci)
docker run -i --rm -e NTFY_URL=<YOUR_VALUE> -e NTFY_TOKEN=<YOUR_VALUE> -e NTFY_PASSWORD=<YOUR_VALUE> ghcr.io/ni-c/ntfy-mcp:0.3.0
Or add to your MCP client config:
{
"mcpServers": {
"ntfy-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"NTFY_URL=<YOUR_VALUE>",
"-e",
"NTFY_TOKEN=<YOUR_VALUE>",
"-e",
"NTFY_PASSWORD=<YOUR_VALUE>",
"ghcr.io/ni-c/ntfy-mcp:0.3.0"
]
}
}
}
NTFY_URLrequired — Base URL of the ntfy server, e.g. https://ntfy.example.net. There is deliberately no default.NTFY_TOKENsecret — ntfy access token (tk_...). Optional: an open instance needs no credentials. Mutually exclusive with NTFY_USERNAME/NTFY_PASSWORD.NTFY_USERNAME— Username for basic authentication. Must be set together with NTFY_PASSWORD.NTFY_PASSWORDsecret — Password for basic authentication. Must be set together with NTFY_USERNAME.NTFY_TOPICS— Comma-separated topics the server may use. The first is the default when a tool omits one, and the list restricts every read and write tool.NTFY_READ_ONLY— Set to exactly true to register only the six read tools (default: false — ntfy exists to publish)NTFY_INSECURE_TLS— Set to true to accept a self-signed certificate from the ntfy server (default: false)NTFY_ALLOW_TOOLS— Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)NTFY_DENY_TOOLS— Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
Related servers
Inbox Zero
Search Gmail and Outlook, save drafts, manage email rules, and view email stats.
lharries/whatsapp-mcp
Search personal WhatsApp messages and contacts, and send messages to individuals or groups.
chigwell/telegram-mcp
Telegram API integration: access user data, manage dialogs (chats, channels, groups), retrieve and send messages, and handle read status.
korotovsky/slack-mcp-server
Slack workspace integration.
emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Microsoft 365 MCP Server
Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Listed in punkpeye/awesome-mcp-servers (MIT)
Data from the Official MCP Registry