Skip to main content
Glama
Sign In
repo-memory-mcp

repo-memory-mcp

by andyast
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to repo-memory-mcp

No user-submitted related servers found.

    Related Servers

    • knock

      HasanGilani
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that gives AI coding agents a persistent code map and memory, so they can retrieve relevant code with exact file:line pointers and rationale instead of re-reading files. It also lets agents save findings for future sessions and flags notes as stale when referenced files change.
      4
      Apache 2.0

    • lxDIG MCP

      lexCoder2
      A
      license
      B
      quality
      C
      maintenance
      MCP server that gives AI coding assistants persistent memory, structural code graph analysis, and safe multi-agent coordination, enabling them to answer architectural questions, track decisions across sessions, and coordinate safely in multi-agent workflows.
      39
      4
      MIT

    • cba

      davidgeorgehope
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for semantic code search and explanation. Allows AI agents to search, ask questions, and manage memory about a codebase with local embeddings and LLM integration.
      -

    • memnant

      peureka
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory MCP server that remembers decisions and context across coding sessions, automatically logging and surfacing relevant knowledge as you work.
      116 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.6/5.0

    Scored across 30 tools

    Disambiguation2/5

    Multiple tools for storing memories (store_memory, propose_memory, remember_project_note, store_decision) and retrieving memories (get_memory, get_memory_with_evidence, search_project_memory, list_memories) have overlapping purposes. Compatibility tools like 'prefer store_memory' add confusion.

    Naming Consistency3/5

    Naming is mostly snake_case with verb_noun pattern, but there are inconsistencies: 'remember_project_note' vs 'store_memory', 'checkpoint_task' vs 'active_checkpoints', and generic 'manage_memory'. The pattern is not fully uniform.

    Tool Count2/5

    30 tools is quite high for a repo memory system. Many are compatibility wrappers or redundant (e.g., delete_memory vs manage_memory). The core functionality could be covered with fewer tools, making the count feel bloated.

    Completeness3/5

    Covers CRUD for memories, search, evidence linking, and checkpoints, but lacks an artifact listing tool. Some lifecycle operations are duplicated. There are notable gaps, but core workflows are supported.

    Resources