Skip to main content
Glama
billy12151

memory-arbiter-mcp

by billy12151
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to memory-arbiter-mcp

No user-submitted related servers found.

    Related Servers

    • tdai-memory-mcp

      tinhien11
      A
      license
      A
      quality
      F
      maintenance
      Local-first MCP memory server that gives AI coding agents long-term memory via SQLite and sqlite-vec, with optional LLM-powered layering. No gateway or API key required.
      7
      102 npm
      4
      MIT

    • Mono Memory MCP

      potato-castle
      A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that provides AI assistants with a shared, persistent SQLite-backed memory for storing and retrieving project context, decisions, and discoveries. It enables cross-session continuity and team-wide knowledge sharing to keep AI coding tools aligned and informed.
      3
      MIT

    • aimem

      yogesh-joshi-0333
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that gives AI coding assistants persistent, project-scoped memory across sessions, storing facts and decisions in a SQLite database under .aimem/ and exposing tools for searching, storing, and conflict-resolving memories.
      26 npm
      MIT
    • threadctx-mcp by threadctx-dev

      threadctx-mcpofficial

      threadctx-dev
      A
      license
      A
      quality
      C
      maintenance
      Shared memory MCP server for AI coding agents, enabling context sharing across sessions with local SQLite or cloud-based semantic search, compatible with Claude Code and Cursor.
      2
      35 npm
      1
      MIT
    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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools are mostly separated by lifecycle stage: daily operations, read-only review, authorized governance, and maintenance. There is some conceptual overlap around conflict inspection, judgment, and resolution across memory, memory_review, and memory_govern, but the descriptions define handoffs well enough for an agent to choose correctly.

    Naming Consistency5/5

    All tool names use lowercase snake_case and share a clear memory_ prefix except the base memory tool. The suffixes review, govern, and repair make each tool's role predictable.

    Tool Count5/5

    Four top-level tools is appropriately compact for a complex memory-management server. Bundling many sub-actions into each tool avoids tool sprawl while keeping high-level categories distinct.

    Completeness5/5

    The surface covers memory creation, retrieval, update, review, governance, conflict handling, maintenance, and repair. No obvious lifecycle gaps or dead ends are apparent for the stated memory-arbiter domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources