Skip to main content
Glama
yanqiw

Coordination Memory MCP

by yanqiw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Coordination Memory MCP

No user-submitted related servers found.

    Related Servers

    • ContextPact

      aniklavida
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and tools to share durable, approved knowledge, current decisions, task ownership, and handoffs from a local-first workspace kept outside any single AI product. Markdown holds human-readable rules, goals, and narratives while SQLite tracks agents, sessions, tasks, leases, and audit events behind one transport-independent core.
      1
      MIT

    • MCP Agent Mail

      Dicklesworthstone
      A
      license
      B
      quality
      A
      maintenance
      A coordination layer for coding agents that provides memorable identities, inbox/outbox messaging, searchable message history, and file lease management to prevent conflicts. Uses Git for human-auditable artifacts and SQLite for fast queries, enabling multiple agents to collaborate across projects without stepping on each other.
      41
      2,192
      MIT

    • JustClone Coordination MCP

      Hazgar2111
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A production-grade coordination hub that enables AI agents and human teams to work as a single organism by sharing tasks, context, decisions, and persistent memory across projects. It features two-tier agentic memory with per-agent hot caches, inter-agent messaging, and multi-agent authorship tracking for seamless collaboration.
      2
      -

    • 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.
      1
      Apache 2.0
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools are grouped clearly by resource type (workspace, run, assignment, event, contract) and many explicitly state role restrictions, so an agent can usually pick the right one. The only real ambiguity is around event-related operations like append_event vs. submit_handoff and review_event vs. accept_event/reject_event.

    Naming Consistency5/5

    All tool names consistently use lowercase snake_case with a predictable verb_noun or verb_qualifier_noun pattern. Get-vs-list is used consistently, and lifecycle actions like create, claim, cancel, seal, reopen, and waive are all recognizable and parallel.

    Tool Count2/5

    At 43 tools, the set is well above the 25+ threshold that makes a surface feel heavy, and an agent must navigate many narrowly scoped, role-gated operations. The domain is complex, but this count still strains selection, recall, and effective tool routing.

    Completeness4/5

    The set covers workspace/team/actor registration, assignment and run lifecycles, event review, human intervention, contracts, invariants, deviations, and verification with few obvious dead ends. Minor gaps remain, such as the lack of a dedicated run-completion tool, no list_events operation, and seal_contract referencing an external deny/second-instance step without a dedicated tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources