Skip to main content
Glama
miles990

claude-dev-memory

by miles990
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to claude-dev-memory

No user-submitted related servers found.

    Related Servers

    • agent-mem0

      ccperdst-lab
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent cross-session memory for Claude Code, enabling it to remember user preferences, decisions, and project context across new sessions.
      Apache 2.0
    • PseudoLife-MCP by Pseudogiant-xr

      PseudoLife-MCPofficial

      Pseudogiant-xr
      A
      license
      A
      quality
      A
      maintenance
      Enables persistent long-term memory for Claude Code across sessions, with tools for storing, searching, and managing facts, knowledge graphs, and procedural lessons.
      35
      82 PyPI
      5
      Apache 2.0

    • tessera

      dr-code
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent codebase memory for Claude Code, enabling semantic understanding of the project structure and action history across sessions to reduce redundant file reads.
      1
      MIT

    • mcp-memvid

      stflj2022
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides long-term memory and lossless context management for Claude Code, enabling automatic context compression, cross-session memory sharing, and semantic search across all history.
      -
    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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct memory operation: recall reads core memory, update writes core memory, archive moves to archival, search queries archival, and status inspects the system. The distinction between recall and search is clear from their descriptions, avoiding ambiguity.

    Naming Consistency5/5

    All tools follow the consistent pattern of 'memory_' prefix followed by a lowercase verb (recall, update, archive, search, status). This predictable naming makes it easy to infer the function of each tool.

    Tool Count5/5

    With 5 tools, the set is well-scoped for a memory management system, covering read, write, archival, search, and status without unnecessary redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of a memory system: accessing core memory, updating it, archiving to long-term storage, searching that storage, and monitoring system state. This is a complete set for the stated purpose, with no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources