Skip to main content
Glama
formonkey

Changes Memory MCP

by formonkey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Changes Memory MCP

No user-submitted related servers found.

    Related Servers

    • mnemo

      JoaquimLegal
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing persistent, local-first memory for AI agents via Markdown files in a git repo, with search, branching, and auditability.
      5 npm
      2
      MIT
    • Ouso Code by Ouso-ai

      Ouso Codeofficial

      Ouso-ai
      F
      license
      Not graded
      quality
      B
      maintenance
      A local, cross-editor MCP server that provides persistent memory for coding agents, capturing and recalling decisions, conventions, and fixes across sessions without API keys.
      -
    • AI Dimag by AiDimag

      AI Dimagofficial

      AiDimag
      A
      license
      A
      quality
      A
      maintenance
      MCP server that gives coding agents persistent, verified memory of codebase decisions, conventions, and skills, with evidence-based claims that are re-checked via git hooks and human-gated review. Enables memory search, propose/approve, chat harvesting, and critique across MCP-compatible tools.
      21
      126 npm
      1
      MIT

    • cookbook-brain

      dpro10
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents persistent, file-based memory stored as plain markdown files in a local git repository, enabling agents to remember, recall, and build on information across sessions.
      6 npm
      1
      MIT

    • memory-mcp

      credp
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server that provides agents with tools to list, read, search, inspect history and diffs, and capture unstructured text in a user-owned Git repository of durable memory.
      5
      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.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools are clearly distinct, but list_changes and list_change_index both list changes, and search_changes vs get_relevant_changes could overlap. Descriptions help clarify the intended use cases, so the ambiguity is limited.

    Naming Consistency5/5

    All tool names follow a consistent verb-first snake_case pattern (e.g., add_local, search_changes, get_change). The add_local/add_global pair uses a predictable scope suffix, and the naming aligns well across the set.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a memory management system. Each tool serves a clear purpose, and the count is within the expected range to avoid unnecessary complexity.

    Completeness3/5

    The server covers creation, retrieval, search, and listing, but lacks update and delete operations for changes. Without these, correcting or removing stored memories is not possible, which is a notable gap in lifecycle coverage.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources