Skip to main content
Glama
TheLBlack

context-ledger

by TheLBlack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to context-ledger

No user-submitted related servers found.

    Related Servers

    • ctxmem

      DoppiaG93
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with persistent, local, and shareable project memory by storing decisions and code context in a searchable SQLite index, supporting keyword and semantic search via MCP.
      121 PyPI
      3
      MIT

    • CodeLedger

      mikuare
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives coding agents a local, SQLite-backed memory of a codebase, enabling them to query symbol impact, change history, and task scope through MCP while recording what actually changed after edits.
      MIT

    • light-agent-memory-mcp-server

      AliYar-Khan
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.
      12
      4 npm
      MIT

    • mcp-chest-memory

      siosig
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent, local-first memory for coding agents over MCP, enabling automatic recall and recording of past work, failures, and decisions to reduce repetition and token usage.
      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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    The four memory tools (search, record, supersede, dispute) each map to a clearly distinct lifecycle action, and descriptions reinforce the boundaries. The only mild overlap is between search_memory and get_file_context, both being retrieval tools, but the file-scoped/parent-directory semantics of get_file_context make them distinguishable.

    Naming Consistency5/5

    All names follow a clean snake_case verb_noun pattern (search_memory, record_memory, supersede_memory, dispute_memory, get_file_context) with no mixing of conventions or vague verbs. The pattern is fully predictable.

    Tool Count5/5

    Five tools is well-scoped for a memory ledger: one create, two retrieval paths, and two state-transition operations. Each tool earns its place without redundancy or obvious bloat.

    Completeness4/5

    The surface covers the core ledger lifecycle: recording, searching, retiring (supersede), and flagging (dispute), plus file-scoped retrieval. Minor gaps exist, such as retrieving a single record by id or listing all memories, but these are workarounds via search rather than hard dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources