Skip to main content
Glama
Sign In
TimEvans

Claude Session MCP

by TimEvans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Claude Session MCP

No user-submitted related servers found.

    Related Servers

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

    • mcp-session-insight

      ArtLjn
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query and analyze past Claude Code sessions, providing structured insights like file changes, decisions, errors, and git history across projects.
      11
      7 npm
      1
      MIT

    • MCP Memory Keeper

      yen16096
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude AI coding assistants to persist and restore context across sessions, including saved findings, decisions, progress, checkpoints, file caches, and searchable topic channels. Supports shared memory across parallel sessions and Git-aware context organization.
      250 npm
      MIT

    • MCP Memory Keeper

      shuhuaa16362
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude AI coding assistants to persist and restore context across sessions, preserving work history, decisions, and progress. It provides checkpointing, search, channels, file caching, and git integration so long-running coding tasks can continue without losing critical information.
      250 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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: checking context budget, retrieving session history, getting session state, recommending context resets, and syncing planning documents. The descriptions clearly differentiate their functions, making misselection unlikely.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (check_context_budget, get_session_history, get_session_state, sync_planning_doc), but 'should_reset_context' deviates slightly by using 'should' instead of a direct action verb. Overall, the naming is readable and predictable with only minor inconsistency.

    Tool Count5/5

    With 5 tools, this server is well-scoped for session management and context tracking. Each tool serves a specific, necessary function in this domain, and the count is neither too thin nor excessive for the apparent purpose.

    Completeness4/5

    The tool set covers core session management needs: monitoring context usage, tracking history and state, providing reset recommendations, and updating planning documents. A minor gap exists in direct context reset or modification tools, but agents can work around this using existing tools like 'should_reset_context' for guidance.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources