Skip to main content
Glama
credp

memory-mcp

by credp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to 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

    • Engram

      rwnalds
      A
      license
      A
      quality
      A
      maintenance
      A self-hosted MCP server that gives AI agents shared, long-term memory over a git-backed folder of markdown, enabling persistent knowledge search, read, and write without a database.
      16
      26 npm
      11
      MIT

    • mem-universe

      H1an1
      A
      license
      A
      quality
      D
      maintenance
      Self-hosted MCP memory server that gives a multi-agent fleet one shared, git-backed memory for search, read, and write.
      8
      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
    • 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
    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.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing, searching, reading, viewing history, and viewing diffs. No two tools overlap in purpose.

    Naming Consistency3/5

    Three tools follow a verb_noun pattern (list_memories, search_memories, read_memory), but history and diff are bare nouns, creating a mixed convention. Still readable but not fully consistent.

    Tool Count5/5

    Five tools is a well-scoped size for a memory management server, providing essential read and inspection capabilities without unnecessary bloat.

    Completeness2/5

    The toolset is read-only, missing create, update, and delete operations for memories. Agents cannot modify the memory store, which is a significant gap for a management server.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources