Skip to main content
Glama

Related Servers

Alternatives to agent_talks

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding-agent sessions on the same machine to collaborate locally and durably by exchanging requests, replies, and task results through an authenticated loopback server with SQLite-backed storage, joined via CLI or an MCP stdio bridge. It also handles message delivery by priority and wait time, deduplicates idempotent sends, enforces task versioning, and preserves artifacts by content hash.
      12 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables two coding agents to exchange tasks, results and bounded goal-driven conversations through a shared local SQLite database over MCP stdio, with atomic claims, expiring leases and optional headless dispatch. It keeps everything local, using no network service and payload-safe diagnostics.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets fleets of long-lived Claude Code sessions coordinate over named channels backed by SQLite, exchanging schema-validated, role-scoped messages that survive restarts, gate actions behind human approval, and leave a queryable audit trail.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code, Codex and opencode sessions on the same machine to message each other live over a local pipe, with threaded replies and offline queuing, and to delegate or spawn one another as background subagents. Messages persist in SQLite and any running server can take over as broker, so peers stay reachable without a daemon.
      97 npm
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code, Codex, and other coding-agent sessions on the same machine to message each other, exchange tracked tasks with owners and states, and coordinate through channels, broadcasts, and multi-session asks without typing into terminals. Messages are routed by what the receiver is doing — next tool call, end of turn, or a held-back digest — so a flood of traffic doesn't interrupt active work.
      254
      14
      56 npm
      1
      MIT