Skip to main content
Glama
serkansmg

smg-claude-memory-mcp

by serkansmg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to smg-claude-memory-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      6 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

    • 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.
      5 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

    B3/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with descriptions that resolve potential overlap. Tools for storing, searching, recalling, updating, and deleting memories are well-differentiated. Retrieval tools (search, recall, list) each target different access patterns.

    Naming Consistency4/5

    All tools start with 'memory_' forming a consistent prefix. However, the second component mixes verb_noun (memory_store, memory_search), noun phrases (memory_project_info), and bare verbs (memory_use), which is somewhat inconsistent. The pattern is more noun-heavy than typical verb_noun conventions.

    Tool Count3/5

    With 24 tools, the server offers extensive functionality, but this exceeds the typical well-scoped range of 3-15. While the domain (memory management with projects, sessions, models, git sync) justifies many tools, the count feels heavy. A reduction or grouping could improve coherence.

    Completeness4/5

    The tool set covers most expected operations for a memory server: CRUD for memories, project management, session handling, model configuration, export/import, and audit trails. Missing features include project deletion and rule editing, which are minor gaps. The surface is largely complete for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources