Skip to main content
Glama
@zeph-to/mcp-server

@zeph-to/mcp-server

by zeph-to

Related Servers

Alternatives to @zeph-to/mcp-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      A 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      An 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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 npm
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.
      2
      15
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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 npm
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data