Skip to main content
Glama
zeph-to

@zeph-to/mcp-server

by zeph-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @zeph-to/mcp-server

No user-submitted related servers found.

    Related Servers

    • CacheBash

      rezzedai
      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

    • MCP Discord Agent

      EugenEistrach
      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

    • call-a-human-mcp

      nishantmodak
      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

    • agent-relay

      cloud1map
      A
      license
      Not graded
      quality
      B
      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.
      9,508 npm
      MIT

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      123 npm
      5
      MIT
    Deploy Server
    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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly distinct: notification history and dismissal tools are separate from sending and interactive-request tools. A few sending-oriented tools (notify vs broadcast, notify vs file, prompt vs input vs ask) could be confused at a glance, but the descriptions clearly define their boundaries.

    Naming Consistency3/5

    All tools share the zeph_ prefix and snake_case naming, which provides a consistent overall look. However, the structure is mixed: some are bare verbs (list, dismiss, notify, ask), some are nouns (clipboard, file), and one is object-verb (session_rename), so the pattern is readable but not fully predictable.

    Tool Count5/5

    11 tools is a well-scoped set for a device-notification and user-interaction server. Each tool has a clear role in sending, receiving, dismissing, requesting input, or managing the session, with no obvious bloat or thinness.

    Completeness5/5

    The tool surface covers the core domain: sending one-way notifications, broadcasting to channels, sending files, prompting for choices, collecting text input, listing/dismissing notifications, copying to clipboard, and renaming sessions. There are no obvious dead ends for typical agent workflows.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources