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
      163 PyPI
      4
      BSD 3-Clause

    • MCP Memory Keeper

      ViktorCosta6156
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables persistent context management for Claude AI coding assistants by saving, searching, checkpointing, restoring, and sharing project context across sessions and parallel conversations.
      250 npm
      MIT

    • Melchizedek

      louis49
      A
      license
      A
      quality
      C
      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
      30 npm
      7
      MIT

    • Claude Soul

      lhuh097
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives Claude Code persistent cross-session memory with semantic search, automatic detection and classification of user corrections into behavioral patterns, and self-evolving frameworks that refine judgment over time. Everything runs locally through hooks and MCP tools, with no cloud, API keys, or telemetry.
      6 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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