@zeph-to/mcp-server
Related Servers
Alternatives to @zeph-to/mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI agents send desktop notifications during tasks, ask for attention, and report completion. Supports macOS, Linux, and Windows, with optional webhook delivery.829-
- AlicenseNot gradedqualityBmaintenanceMCP server enabling real-time communication, task delegation, and acknowledgment among multiple AI agents through a single local endpoint.117 npm6MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that coordinates AI coding agents with mobile notifications, enabling task queues, inter-agent messaging, session monitoring, and human-in-the-loop approvals.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to send notifications and request user input via Discord during long-running tasks. It allows users to remotely interact with their AI assistants and provide feedback through the Discord messaging platform.26 npm2MIT
- AlicenseAqualityAmaintenanceAn MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.215Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents on different machines to communicate and collaborate directly through relay channels, supporting structured agent contracts, real-time messaging, and human-in-the-loop approval workflows.3,505 npm1MIT
TDQS
Scored across 10 tools
Most tools map to distinct communication/notification actions, and descriptions clarify the recipient and medium. zeph_notify, zeph_broadcast, zeph_file, and zeph_clipboard all deliver content to devices and could be confused at a glance, though their purposes are ultimately different.
All tools share the zeph_ prefix, but the naming convention varies: some are bare verbs (zeph_notify, zeph_ask), some are nouns used as actions (zeph_file, zeph_clipboard), and some are object_verb (zeph_agent_send, zeph_session_rename). This is readable but not a predictable pattern.
Ten tools is well-scoped for a device notification and messaging server. The set covers sending, listing, dismissing, asking, file transfer, clipboard, agent messaging, and session naming without feeling bloated or redundant.
The core notification lifecycle (send/list/dismiss/dismiss_all) and key communication paths (ask, file, agent send) are present. Channel management is delegated to a resource and there is no explicit notification update, but these are minor gaps rather than blockers.