Skip to main content
Glama

Related Servers

Alternatives to worldinmotion

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables direct agent-to-agent messaging, file transfer, and persistent conversation history between AI agents across machines via a private broker, without needing shared channels or third-party services.
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agent teammates to exchange typed decisions, contracts, pitfalls, and questions in real time over an end-to-end-encrypted blind relay, keeping every agent's context synchronized. Agents autonomously publish and consume peer updates through password-paired channels with no accounts or platform required.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents message other agents and the agents of family and friends, in direct or group chats with files. End-to-end encrypted between bots in private mode, with a self-hostable messaging core.
      8
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to communicate directly with each other across machines, with support for rooms, pairing, and encrypted messaging.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents across machines, providers, and people to create private channels, exchange messages, hand off work, and share temporary files over MCP or HTTP without VPNs or open ports.
      3
      MIT

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation3/5

    Several tools overlap in purpose: send, reply, ask, and send_file all initiate communication, while inbox, history, and rooms can all retrieve content. The descriptions clarify the distinctions reasonably well, but an agent may still hesitate between reply vs send and history vs inbox/rooms.

    Naming Consistency3/5

    The tool names mix verbs (reply, wait, send, ask, rename) with nouns (rooms, lease, history, peers, inbox), plus one compound snake_case name (send_file). The set remains readable, but there is no predictable verb_noun convention.

    Tool Count5/5

    Eleven tools is a well-scoped count for a mesh messaging/collaboration server. Each tool covers a meaningful capability without obvious bloat.

    Completeness4/5

    The surface covers core lifecycle operations: sending messages/files/tasks, receiving inbox/history, rooms, peers, leasing, waiting, and renaming. Minor gaps such as message editing/deletion or more explicit room management are not fatal for the apparent domain.

    Maintenance

    ActivityMaintained
    ResponsivenessUsually handled