Skip to main content
Glama
diaz3618

memory-bank-mcp

by diaz3618
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to memory-bank-mcp

No user-submitted related servers found.

    Related Servers

    • Project Brain

      myczh-1
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP memory server that gives AI assistants durable project memory across coding sessions, storing context, changes, and decisions.
      3 npm
      1
      MIT

    • TIMPS

      TIMPSs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.
      13 npm
      MIT

    • Hindsight

      LeoYueDev
      A
      license
      Not graded
      quality
      B
      maintenance
      Open-source MCP server that gives AI coding assistants persistent memory, recording conversations and file changes to build user profiles and provide context across sessions.
      32 npm
      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
    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

    B3.2/5.0

    Scored across 36 tools

    Disambiguation5/5

    Each tool targets a specific operation (e.g., adding progress, reading files, managing knowledge graph) with detailed descriptions that clearly differentiate their purposes. Overlap is minimal and well-documented.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., add_progress_entry, batch_read_files, graph_upsert_entity), making the set predictable and easy to navigate.

    Tool Count2/5

    36 tools is well above the typical well-scoped range of 3-15, making the surface feel heavy. While many tools are individually useful, the count suggests the server may be trying to cover too many subdomains.

    Completeness4/5

    Core CRUD operations for files and knowledge graph, progress tracking, backups, and search are covered. However, there is no explicit file deletion tool, which represents a minor gap in an otherwise complete surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources