Skip to main content
Glama
SEARO1

Agent Cross-Session MCP

by SEARO1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Agent Cross-Session MCP

No user-submitted related servers found.

    Related Servers

    • AgentMesh

      microinginer
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables already-running AI coding agents on the same project to register, discover one another, and exchange durable direct messages so they can share progress and avoid conflicting work.
      Apache 2.0

    • 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
      13 npm
      2
      AGPL 3.0

    • slm-mesh

      qualixar
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.
      49 npm
      19
      Elastic 2.0

    • sangam

      uditjainstjis
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents on different machines to share verbatim session context and coordinate file leases, preventing concurrent edits and allowing each agent to query the other's exact actions and words.
      MIT

    • beacon

      a1473838623
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides real-time presence and collision avoidance for parallel AI coding agents, allowing them to report and query activities to avoid overlapping edits and destructive git operations.
      31 npm
      4
      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 6 tools

    Disambiguation5/5

    Each tool targets a distinct slice of cross-session awareness: peers (all sessions at a glance), session_detail (one session's timeline), whoami (self), overlaps (collision risk), announce/board (write/read notes). The descriptions explicitly cross-reference each other ('Use it after peers', 'Other sessions read it with board'), making selection unambiguous.

    Naming Consistency3/5

    Names are readable but follow no single convention: session_detail uses snake_case while peers, overlaps, announce, board, and whoami are bare single words mixing nouns (peers, board) with verbs (announce) and a question-style identifier (whoami). Predictable enough to navigate, but not a consistent verb_noun pattern.

    Tool Count5/5

    Six tools is well-scoped for a cross-session coordination server: three read/awareness tools, two messaging tools, and one identity tool. Every tool earns its place with no redundant surface.

    Completeness4/5

    The surface covers the core lifecycle — discover sessions, inspect activity, detect collisions, broadcast notes, read notes, and identify self. Minor gaps exist: no targeted messaging to a specific session, no reply/threading on the board, and no way to clear or expire notes.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources