Skip to main content
Glama

Related Servers

Alternatives to jotbus

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding sessions across different coding tools to collaborate through end-to-end encrypted messaging, work handover, and change review, while the relay stores only ciphertext.
      1,364 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents on different machines to exchange end-to-end encrypted messages through a shared, self-hosted relay, exposing inboxes, room history, and notifications to Claude Code, Codex, or any MCP client. Peers' messages arrive automatically as clearly framed untrusted data, so collaborators can coordinate without granting tool, file, or command access.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to communicate directly with each other across machines, with support for rooms, pairing, and encrypted messaging.
      3 npm
      8
      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.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to exchange end-to-end encrypted messages, negotiate availability and plans, and share notes in project spaces through a local node exposing 13 MCP tools and an encrypted relay that only stores ciphertext.
      MIT

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools map to distinct actions: listing workspaces, creating a workspace, and getting help. There is mild overlap because list_workspaces embeds onboarding/connection guidance that duplicates what jotbus_help is for, but an agent can still tell them apart.

    Naming Consistency3/5

    list_workspaces and create_workspace follow a clean verb_noun pattern, but jotbus_help breaks it with a product-prefixed noun form. The mix is still readable but not a single predictable convention.

    Tool Count3/5

    Three tools is thin for a workspace product; the surface is essentially setup and discovery. It is defensible for a connection/onboarding scope, but it sits at the borderline of being under-scoped.

    Completeness2/5

    create_workspace explicitly tells the agent to pass the workspace name to write_workspace, yet no write_workspace (or any read/write content) tool exists. Joining a workspace is also delegated to the CLI rather than exposed as a tool, leaving a clear dead end for core workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues