Skip to main content
Glama
jarmstrong158

context-keeper

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to context-keeper

No user-submitted related servers found.

    Related Servers

    • Cortex

      cdeust
      A
      license
      C
      quality
      A
      maintenance
      Stores and recalls Claude Code session content as persistent memory, auto-injects relevant prior decisions and lessons at session start, and exposes 33 MCP tools for memory, knowledge-graph navigation, and cognitive profiling — backed by 41 neuroscience papers and 97.8% R@10 on LongMemEval.
      40
      6 npm
      380 PyPI
      73
      MIT

    • Cortex

      ProductionLineHQ
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.
      176 npm
      1
      MIT

    • claude-handoff

      Vasilispapg
      A
      license
      A
      quality
      A
      maintenance
      Post-hoc session handoff and project memory for Claude Code: MCP tools list_sessions and handoff turn any session — even crashed or usage-limit-hit ones — into a clean handoff.md another model can continue from, with secrets redacted from every output. Zero dependencies, fully local; also distills a project's entire session history into one cited memory brief.
      2
      2
      1
      MIT

    • NotNessie MCP Server

      GreXLin85
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to persist and retrieve project memory across sessions, including decisions, constraints, verified commands, and context packs, via nine MCP tools.
      2
      MIT

    • AI Memory MCP

      w693847022
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent project memory MCP server for Claude Code that remembers development context across sessions, including features, fixes, notes, and standards.
      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

    A3.9/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creation, retrieval by relevance, structured filtering, overview, snapshot export, update, deprecation, stale pruning, compaction reporting, quality verification, markdown export, constraint reloading, snapshot import, and remote sync. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., record_entry, get_context, export_snapshot). The single verb 'mirror' is common and fits the pattern of operations.

    Tool Count5/5

    14 tools cover the full scope of context management without bloat. Each tool addresses a specific need (CRUD, maintenance, export/import, sync) and the count is appropriate for the domain.

    Completeness5/5

    The tool surface covers the full lifecycle: create, read (multiple modes), update, deprecate, export/import, sync, maintenance (pruning, quality checks), and constraint management. No obvious gaps for the stated purpose of project context management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources