Skip to main content
Glama
kunwar-shah

ClaudeX

by kunwar-shah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ClaudeX

No user-submitted related servers found.

    Related Servers

    • Longhand

      Wynelson94
      A
      license
      A
      quality
      A
      maintenance
      Persistent local memory for Claude Code that indexes every session's JSONL file verbatim into SQLite + ChromaDB. Exposes 17 MCP tools for semantic recall, deterministic file replay, and fuzzy "do you remember when..." queries across your entire session history — no API calls, nothing leaves the machine.
      17
      128 PyPI
      14
      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.
      6 npm
      4
      MIT

    • Melchizedek

      louis49
      A
      license
      A
      quality
      B
      maintenance
      Persistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.
      16
      34 npm
      7
      MIT

    • memory-mcp

      AyubMoh1
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory MCP server for Claude Code. Store, search, and retrieve memories across sessions using hybrid vector + keyword search powered by SQLite, FTS5, and sqlite-vec.
      20 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

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. Overlap exists between list_memories and recall_memory, but they serve different retrieval needs (stats vs. priority/recency). Similarly, get_session_summary is a cheaper alternative to get_session. Overall, no two tools are ambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., delete_memory, list_sessions, search_conversations). The pattern is predictable and easy to parse.

    Tool Count5/5

    10 tools is appropriate for this domain, covering memory management, session tracking, and project awareness. Each tool serves a necessary function without unnecessary bloat.

    Completeness4/5

    The tool set covers the core lifecycle of memories (create, read, delete) and sessions (list, read, search, summarize). A minor gap is the lack of an explicit memory update tool, though store_memory can overwrite. Overall, the surface is complete for its stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources