Skip to main content
Glama
leesgit

claude-session-continuity-mcp

by leesgit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to claude-session-continuity-mcp

No user-submitted related servers found.

    Related Servers

    • ORA

      black-dash77
      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

    • Session Buddy

      lesleslie
      A
      license
      A
      quality
      B
      maintenance
      Provides comprehensive session management for Claude Code with automatic initialization/cleanup, quality checkpoints, and local conversation memory with semantic search for capturing learnings across coding sessions.
      6
      631 PyPI
      2
      BSD 3-Clause

    • 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
      28 npm
      7
      MIT

    • mcp-memvid

      stflj2022
      F
      license
      C
      quality
      D
      maintenance
      Provides long-term memory and lossless context management for Claude Code, enabling automatic context compression, cross-session memory sharing, and semantic search across all history.
      10
      -
    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/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: session vs. project vs. task vs. memory vs. verification clusters are well separated. Minor overlap exists between memory_search and memory_related (both retrieve memories) and session_history vs search_sessions, but descriptions clarify the difference well enough.

    Naming Consistency4/5

    The vast majority use snake_case verb_noun (session_start, task_list, verify_build, memory_store). A few deviate (search_sessions, list_projects) where the verb comes first, and the memory_* vs graph_* split is coherent. Overall predictable and readable.

    Tool Count3/5

    At 25 tools this is on the heavy side, but the surface area is broad—session continuity, project state, tasks, solutions, verification, memory, and graph relationships. Each tool serves a distinct purpose, though some could be merged (e.g., verify_build/test/all could be one parameterized tool).

    Completeness3/5

    The surface covers session, project, task, solution, verification, and memory workflows, but there are notable lifecycle gaps: no delete or update for sessions/projects/memories/solutions, and no standalone lint verification despite verify_all including lint. Task management lacks a delete tool. These gaps make some workflows dead-end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources