ntfy MCP server—reach the operator on their phone and wait for a reply before continuing
MCP MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. ntfy MCP server—reach the operator on their phone and wait for a reply before continuing.
Email and Slack are heavy for a quick “deploy finished” or “approve this?” Mobile push is instant, but agents do not have a standard way to use it. ntfy is simple HTTP; this server bridges MCP ↔ ntfy so the model can reach you and read your answer back.
Once MCP is connected, these are the calls the assistant has available:
TypeScript — small, functional layout (ntfy client, notify service, separated prompts)Variable — RequiredNTFY_SERVER_URL — YesNTFY_TOPIC — YesNTFY_POLL_WINDOW_MS — Nomessage — Yestitle — NoSituation — Use notifyYou will need 2 environment variables: NTFY_SERVER_URL, NTFY_TOPIC. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — TypeScript, Variable, NTFY_SERVER_URL and 5 more — is a fair guide to whether it matches your workflow. It is maintained by birajmainali; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| TypeScript | small, functional layout (ntfy client, notify service, separated prompts) |
| Variable | Required |
| NTFY_SERVER_URL | Yes |
| NTFY_TOPIC | Yes |
| NTFY_POLL_WINDOW_MS | No |
| message | Yes |
| title | No |
| Situation | Use notify |
{
"mcpServers": {
"ntfy-1": {
"command": "npx",
"args": ["-y", "mcp-server-ntfy"],
"env": {
"NTFY_SERVER_URL": "your-value",
"NTFY_TOPIC": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| NTFY_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
| NTFY_TOPIC | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.