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
      C
      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.
      MIT

    • MCP Agent Mail

      Dicklesworthstone
      A
      license
      Not graded
      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.
      2,132
      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
      -

    • agent-memory-os

      yamantaka520
      A
      license
      A
      quality
      A
      maintenance
      Local-first memory engine for AI-agent teams: private/team/project ACL, associative recall, and federated sync across nodes. One SQLite file, no LLM required.
      12
      5
      Apache 2.0
    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

    C2.8/5.0

    Scored across 42 tools

    Disambiguation3/5

    Most operations target distinct entities and lifecycle stages, and descriptions are generally explicit. However, accept_event/reject_event sit alongside the more general review_event, and cancel_assignment/supersede_assignment plus record_run_binding/append_event/submit_handoff create overlapping clusters that could cause misselection in a 42-tool surface.

    Naming Consistency4/5

    Names are uniformly snake_case and mostly follow a verb_noun shape (list_workspaces, create_assignment, seal_contract), which is easy to scan. Minor inconsistencies such as register_actor/register_workspace vs create_team, and noun-verb exceptions like heartbeat_run/checkpoint_run, keep it from being fully consistent.

    Tool Count2/5

    Forty-two tools is well beyond the 25+ threshold and makes the surface heavy for an agent to navigate, even for a complex coordination domain. Several near-duplicate decision/event tools could be consolidated or grouped into sub-servers without losing capability.

    Completeness4/5

    The set covers the core coordination lifecycle well: registration, assignment claiming, run heartbeats, interventions, event review, contract creation/sealing/evaluation, verification, snapshots, and export. Missing direct reads for actors/teams and absence of unarchive/delete operations are minor gaps, but most workflows don't hit dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources