Skip to main content
Glama
michael-denyer

Memory MCP Server

by michael-denyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Memory MCP Server

No user-submitted related servers found.

    Related Servers

    • CCCMemory MCP

      xiaolai
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides Claude with long-term memory by indexing conversation history, enabling semantic search, decision tracking, and cross-project search.
      18 npm
      29
      MIT

    • coding-memory-mcp

      ChinaCarlos
      A
      license
      Not graded
      quality
      D
      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.
      6 npm
      2
      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.
      18 npm
      4
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 56 tools

    Disambiguation3/5

    There are multiple tools for similar purposes (e.g., recall, recall_by_tag, recall_with_fallback; find_contradictions, get_contradictions, mark_contradiction), but descriptions help differentiate them. Some overlap exists, especially among recall variants and validation/invalidation tools.

    Naming Consistency3/5

    Naming conventions are mixed: some use verb_noun (e.g., list_memories, link_memories), others are phrases or single verbs (e.g., remember, forget, hot_cache_status). While most are readable, the pattern is not uniform.

    Tool Count2/5

    56 tools is excessive for a single server. Many tools are specialized variants or internal utilities (e.g., db_info, metrics_status) that could be consolidated. The high number makes the tool surface hard to navigate.

    Completeness4/5

    The tool set covers the full lifecycle of memory management: storage, recall, validation, relationships, contradictions, hot cache, sessions, mining, consolidation, and maintenance. Only minor gaps exist (e.g., batch operations on memories could be more explicit).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources