mcp-notify
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NOTIFY_API_URL | No | Backend API URL | https://api.mcpnotify.dev/v1 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pair_deviceA | Pair your phone to receive notifications. Displays a QR code to scan with the MCP Notify mobile app. This is the first step for new users. |
| check_pairing_statusA | Check if the QR code has been scanned and pairing is complete. Use this after displaying a QR code. |
| get_setup_statusA | Check if MCP Notify is set up and ready to send notifications. Returns pairing status and device count. |
| send_notificationA | Send a push notification to your paired devices. Use this when the user asks to be notified about something. |
| get_historyA | View your recent notification history. |
| get_quotaA | Check your notification quota and usage. Shows how many notifications you can send this month. |
| list_devicesA | List all paired devices that can receive notifications. |
| remove_deviceB | Remove a paired device. It will no longer receive notifications. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools target clearly distinct actions: pairing, sending, history, quota, and device management. The only mild overlap is between check_pairing_status and get_setup_status, but their descriptions differentiate an in-progress QR scan from overall readiness.
All tool names follow a consistent verb_noun pattern in snake_case, such as pair_device, send_notification, get_history, and remove_device. The verbs are clear and the pattern is predictable throughout.
Eight tools is a well-scoped size for a notification server, covering setup, sending, status, history, quota, and device management without unnecessary redundancy. Each tool earns its place.
The surface covers the full notification lifecycle: pairing, setup verification, sending, history, quota monitoring, device listing, and device removal. No obvious blocking gaps exist for the stated purpose.