mcp-pushinator

Related Servers

Alternatives to mcp-pushinator

No user-submitted related servers found.

Related Servers

mcp-os-notifications
ekomac
A
license
B
quality
C
maintenance
An MCP server that lets LLM agents dispatch native OS notifications when a task finishes. It supports cross-platform desktop notifications, task tokens for updates, mobile bridges, and quiet hours.
Updated 2 months ago (2026-07-18 15:59 UTC)
2
MIT
Pushary Agent Skillofficial
Developer Tools Communication Agent Orchestration
Pushary
A
license
Not graded
quality
B
maintenance
Pushary is an MCP server that connects AI agents to push notifications, enabling human-in-the-loop approval from a phone.
Updated 5 days ago (2026-09-26 11:39 UTC)
1
MIT
mcp-ding
OS Automation Developer Tools
zhuqingyv
F
license
Not graded
quality
D
maintenance
MCP server for macOS native notifications with 67 AI brand icons and system sound support, enabling AI agents to send desktop notifications via one-line tool calls.
Updated 6 months ago (2026-04-07 06:41 UTC)
-
ntfy MCP Server
hexerei
A
license
Not graded
quality
D
maintenance
Send push notifications to mobile devices via ntfy.sh from AI assistants.
Updated a year ago (2025-10-20 16:38 UTC)
MIT
macOS Notification MCP
OS Automation Text-to-Speech App Automation
devizor
A
license
Not graded
quality
C
maintenance
macOS Notification MCP enables AI assistants to trigger native macOS sounds, visual notifications, and text-to-speech. Built for Claude and other AI models using the Model Context Protocol.
Updated a year ago (2025-05-09 17:51 UTC)
37
MIT
MCP-Pushover Bridge
Communication App Automation
pyang2045
A
license
B
quality
D
maintenance
Enables AI assistants to send push notifications to mobile devices via Pushover, allowing users to receive instant alerts for task completions, errors, reminders, and custom messages through their AI conversations.
Updated a year ago (2025-06-25 05:30 UTC)
1
13 npm
2
MIT

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored 2026-04-18 10:40 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as sending notifications via the Pushinator API, making it distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'send-notification' follows a clear verb-noun pattern, and there are no other tools to compare it against for inconsistency.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. While it could be appropriate for a very simple notification service, it often feels thin and lacks the depth needed for typical agent workflows.

Completeness3/5

Inferring the domain as notification sending, the tool covers the core action of sending notifications. However, there are likely gaps such as managing notification settings, retrieving sent notifications, or handling errors, which could lead to incomplete workflows for agents.