Skip to main content
Glama
timmx7
by timmx7

Related Servers

Alternatives to acheron-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude to remember conversations and learn over time by storing and recalling messages, memory abstracts, and recent history using a local SQLite database.
      4
      21 npm
      72
      MIT
    • 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
      31
      MIT
    • 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
      33 npm
      7
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Persistent memory + intelligent context for Claude Code. Save and reuse solutions, decisions, and patterns across projects.
      43
      7
      MIT
    • A
      license
      A
      quality
      B
      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

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action (save, get, list, search, delete, status) on contexts with no overlap. The descriptions clearly differentiate when to use each.

    Naming Consistency5/5

    All tool names follow a consistent pattern: bridge_verb_context (e.g., bridge_save_context, bridge_list_contexts). The verbs are clear and uniform.

    Tool Count5/5

    Six tools cover the essential operations for a context management system (CRUD plus search and overview) without being excessive or sparse.

    Completeness4/5

    The tool set provides create, read, list/ browse, search, delete, and status. An update operation is missing, but contexts may be intended as immutable entries, making the set largely complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues