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
      126 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.
      30 npm
      MIT
    • threadctx-mcp by threadctx-dev

      threadctx-mcpofficial

      threadctx-dev
      A
      license
      A
      quality
      B
      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
      39 npm
      1
      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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools are mostly distinct: review is read-only, govern is state-changing, repair is maintenance, and memory is daily operations. Some overlap exists between govern and repair (both can handle conflicts/duplicates), but the descriptions clarify the intended separation.

    Naming Consistency4/5

    All tool names use a consistent memory_ prefix with a single verb (review, govern, repair, memory). The pattern is predictable, though the fourth tool 'memory' breaks the verb_noun convention by repeating the server name instead of using an action verb.

    Tool Count4/5

    Four tools is a reasonable, focused count for a memory management server. Each tool is broad with many sub-actions, so the count feels slightly thin but appropriate given the consolidated command surface.

    Completeness4/5

    The tool set covers the core memory lifecycle: create/read/update/find, review, conflict resolution, and maintenance. Minor gaps exist (no explicit delete/destroy action visible, and some sub-actions are hidden behind help), but the surface appears functionally complete for its domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources