Skip to main content
Glama
navid-kianfar

Claude Memory MCP

by navid-kianfar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Claude Memory MCP

No user-submitted related servers found.

    Related Servers

    • smg-claude-memory-mcp

      serkansmg
      A
      license
      B
      quality
      D
      maintenance
      Persistent, searchable project memory for Claude Code. Each project has its own local DuckDB with vector embeddings, auto-loading context at session start.
      24
      33
      MIT

    • claude-memory

      Tim-Fischer-zh
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.
      8 npm
      4
      MIT

    • cc-history

      Straska7
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides local-first, cross-session memory for Claude Code, enabling semantic search across past sessions to retrieve procedures, decisions, or answers without exposing secrets.
      Apache 2.0

    • ClaudeX

      kunwar-shah
      A
      license
      A
      quality
      C
      maintenance
      Persistent memory + FTS5 full-text search for Claude Code conversation history. Indexes ~/.claude/projects/ JSONL into SQLite, exposes 10 MCP tools (store/recall/search memories, browse sessions, get summaries) plus prompts. Includes a web UI for visual exploration
      10
      42 npm
      93
      MIT

    • coding-memory-mcp

      ChinaCarlos
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.
      12 npm
      2
      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 37 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose, with names like memory_store, memory_search, memory_add_rule, and memory_session_start all targeting different operations. While there are many tools, descriptions ensure they are easily distinguished, and there is no ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'memory_<verb>_<noun>' pattern (e.g., memory_list_projects, memory_init_project, memory_add_rule, memory_session_end). No mixing of conventions, making it predictable and easy to navigate.

    Tool Count4/5

    37 tools is higher than typical but justified by the broad scope: project management, memory CRUD, rules, templates, sessions, import/export, and model configuration. A slight reduction could improve simplicity, but it remains well-scoped for the domain.

    Completeness5/5

    The tool surface covers the full lifecycle of memory management: create/read/update/delete for memories, projects, and rules, plus sessions, templates, import/export, and version checking. No obvious gaps for the intended purpose of a persistent memory server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources