Skip to main content
Glama
johannschiffer

AgentMesh MCP

by johannschiffer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AgentMesh MCP

No user-submitted related servers found.

    Related Servers

    • JEVULON VII (JVII)

      Jason-Fay
      A
      license
      A
      quality
      C
      maintenance
      Enables parallel AI coding agents to claim files atomically, detect and prevent workspace collisions, and receive deterministic zero-latency safety verdicts on destructive shell commands without any network egress. It also provides autonomous wave dispatch, worker recovery, and completion verification for multi-agent workflows via a shared coordination board.
      7
      7 npm
      MIT

    • TaskSwarm

      Wersky
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to decompose a goal into a dependency-aware task tree, atomically claim and update tasks across parallel subagents in dependency waves, and coordinate through a shared progress board with paged notes and crash-safe, lock-protected persistence.
      MIT

    • agentcheckpoint

      erniomaldo
      A
      license
      A
      quality
      D
      maintenance
      An atomic key-value store for AI agent coordination, ensuring agents always work with the latest state.
      5
      24 PyPI
      MIT

    • Pursers

      swisspra
      A
      license
      Not graded
      quality
      A
      maintenance
      Local OS for your AI Agents fleets. ——————- Enables AI agents to coordinate through a durable local board with shared state, ticket lifecycle, evidence-based approvals, and journal-woken handoffs.
      2
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct action in the task lifecycle: create, claim, complete, fail, get, list, and board status. The boundaries between query tools (get_task for a single ID vs list_tasks for filtered sets) and mutation tools are clear, so an agent can select confidently.

    Naming Consistency5/5

    Every tool follows a consistent verb_noun snake_case pattern (create_task, claim_task, complete_task, fail_task, get_task, list_tasks, get_board_status). No deviations in style or casing.

    Tool Count5/5

    Seven tools is well-scoped for a swarm task board, with each tool earning its place across create/read/state-transition operations. No redundancy or filler.

    Completeness4/5

    The core task lifecycle (create, claim, complete, fail) plus read/query operations is fully covered. Minor gaps exist, such as releasing/unclaiming a task or updating task fields (priority, metadata), but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources