Skip to main content
Glama
GrigoriLab

claude-mux-iterm

by GrigoriLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to claude-mux-iterm

No user-submitted related servers found.

    Related Servers

    • claudechat

      zzibo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code agents to communicate across sessions, terminals, and repositories through shared channels with persistent context.
      MIT

    • claude-intercom-mcp

      dataforxyz
      A
      license
      A
      quality
      B
      maintenance
      Enables local messaging between Claude Code, Codex, Pi, and other coding-agent sessions on the same machine, allowing them to discover each other, send updates, ask questions, and reply.
      8
      9 npm
      2
      AGPL 3.0

    • claude-session-bus

      exalsch
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code sessions sharing a project root to broadcast short messages to each other via a JSONL mailbox, with sending as an MCP tool and receiving as a prompt hook.
      GPL 3.0
    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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: registration, listing sessions, unicast, broadcast, listing messages, and acknowledging. No two tools could be confused, even though send_message and broadcast_message share the sending concept, their targets differ.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern with snake_case, using consistent verbs like register, list, send, broadcast, and acknowledge. The naming is predictable and readable.

    Tool Count5/5

    Six tools is well-scoped for a session management and messaging system. Each tool contributes to the core workflow without redundancy or bloat.

    Completeness4/5

    The core lifecycle is covered: register, discover, send, broadcast, read, and acknowledge. A notable gap is the lack of an unregister_session or cleanup mechanism, which could leave stale sessions, but agents can work around this in practice.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources