Skip to main content
Glama
MikeyBeez

MCP Continuation Notes

by MikeyBeez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP Continuation Notes

No user-submitted related servers found.

    Related Servers

    • Baton

      timurabi3
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to hand off in-progress work across sessions and different MCP clients by persisting shared state and handoff notes in a project folder.
      6
      MIT

    • handoff-mcp

      m053m716
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent sessions to persist and reload project-scoped handoffs and todos across sessions, preserving context and tracking next steps.
      MIT

    • ai-cortex

      ai-creed
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides durable project context for coding agents, including project maps, session history, and explicit memories, all stored locally.
      64 npm
      7
      MIT
    • never4ga-mcp by BezaCore-Labs

      never4ga-mcpofficial

      BezaCore-Labs
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents and MCP clients to start each session with a pre-assembled context pack of the project's Markdown notes, decisions, rules, Git and tracker state, and to write progress and decisions back as dated logs. Context is gathered locally by lookups and queries rather than model calls, so different tools like Claude Code, Codex, and Antigravity share the same memory without spending tokens on retrieval.
      15
      134 PyPI
      1
      Apache 2.0
    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 7 tools

    Disambiguation4/5

    Tools are mostly distinct: write, read (three variants), delete, check, list. The three read tools overlap slightly, but their intended use cases are clearly described (read-and-cleanup, read-with-staleness, read-without-staleness) and one is deprecated, reducing ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent pattern: continuation_ prefix plus a verb phrase (write, read_and_cleanup, read_with_staleness, cleanup_old, check_handoff, list_for_project, read_project_note). The naming is perfectly uniform and predictable.

    Tool Count5/5

    With 7 tools, the server is well-scoped for the single purpose of managing continuation notes. Each tool serves a clear lifecycle function (write, read, check, list, delete) without bloat or redundancy.

    Completeness5/5

    The tool set covers the full continuation‑note lifecycle: creation (write), retrieval (read variants), existence checking, listing for a project, and deletion. No obvious gaps exist; the write tool replaces previous notes, so an explicit update is unnecessary.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources