ntfy-notify
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTFY_TOKEN | No | Bearer token for protected / self-hosted topics. | |
| NTFY_TOPIC | Yes | Your long, random topic. Never hardcoded. | |
| NTFY_BASE_URL | No | Set to your own host if self-hosting. | https://ntfy.sh |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_notificationA | Send a push notification to the configured ntfy topic (your phone). Args: message: The notification body text. title: Optional bold title shown above the message. priority: One of min, low, default, high, urgent (or "1".."5"). Anything unrecognized falls back to "default". tags: Comma-separated emoji shortcodes, e.g. "tada,computer". click_url: Optional URL opened when the notification is tapped. Returns: A status string starting with "OK:" on success or "FAILED:" on error. |
| send_job_alertA | Send a job-search inbox-sweep summary with sensible defaults. Thin wrapper around send_notification: title "Job sweep", high priority, a briefcase tag. Intended for the daily job-inbox-sweep task. Args: summary: The summary text to push to your phone. Returns: A status string starting with "OK:" on success or "FAILED:" on error. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Gardner-Programs/ntfy-notify'
If you have feedback or need assistance with the MCP directory API, please join our Discord server