Skip to main content
Glama
yesitsfebreeze

mesh

by yesitsfebreeze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mesh

No user-submitted related servers found.

    Related Servers

    • xtalk

      8w6s
      A
      license
      B
      quality
      B
      maintenance
      Cross-agent messaging for MCP clients, enabling agents to discover one another, exchange threaded messages, and resume work in a persistent project room.
      19
      1
      MIT

    • agent-comms-mcp

      redesignhealth
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for permissioned, structured agent-to-agent communications, enabling agents to coordinate and negotiate through scoped, typed messages with authentication and audit logging.
      1,004 PyPI
      MIT

    • agent-hub

      zzf-hash
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for universal multi-agent communication, enabling agents to register, send/receive messages, manage tasks, and coordinate via role-based routing with project isolation.
      2 npm
      ISC

    • Axis

      VirSanghavi
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for coordinating multiple AI agents across developers and vendors with a shared job board, per-file locking, and live project context.
      5
      AGPL 3.0

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      123 npm
      5
      MIT

    • ACDP

      gabogabucho
      A
      license
      A
      quality
      D
      maintenance
      Enables multiple AI agents to coordinate work on the same codebase by providing real-time file locking, commit approval, and agent awareness through a lightweight WebSocket-based MCP server.
      9
      10 npm
      11
      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

    B3.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct operation: locking, inspecting, garbage collection, peeking, sending, reading, registering, releasing, and listing. Descriptions clearly differentiate them, with no overlapping purposes.

    Naming Consistency4/5

    Most tool names are single-word verbs, but 'gc' is an abbreviation and 'roster' is a noun, introducing slight inconsistency. However, the pattern is largely predictable.

    Tool Count5/5

    With 9 tools, the server covers essential operations for messaging and locking without superfluous tools. The count feels well-scoped.

    Completeness4/5

    The tool set provides full lifecycle for messages (post, read, inbox, gc) and locks (claim, claims, release), plus presence (register, roster). Minor missing features like explicit message deletion or broadcast-only send could be present but are not critical gaps given descriptions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources