Skip to main content
Glama
Oshadha345

contxt-box

by Oshadha345
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to contxt-box

No user-submitted related servers found.

    Related Servers

    • promem-mcp

      DIP-RO
      A
      license
      B
      quality
      A
      maintenance
      Enables AI coding agents to maintain persistent project context, including rules, decisions, environment intelligence, and Git history, using a local-first MCP server with automatic project detection and token-efficient retrieval.
      13
      MIT

    • Recalloom

      RavelloH
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store, search, version, and precisely edit context across sessions using virtual folders, tags, structured TODOs, semantic retrieval, and revision history via MCP.
      MIT

    • Sugar

      nKimura51
      F
      license
      Not graded
      quality
      A
      maintenance
      Provides local-first, cross-session persistent memory that lets AI coding agents store, semantically search, and recall project-specific and cross-project knowledge via MCP tools and resources, with an optional task queue for autonomous execution.
      -

    • agents-memory

      Lolaplex
      A
      license
      Not graded
      quality
      A
      maintenance
      A local markdown memory and cross-agent context engine for AI coding assistants. It provides an MCP server with tools to search, add, retrieve, and distill persistent memory across tools like Claude Code, Cursor, and Zed.
      37 PyPI
      5
      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/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct purposes (e.g., auto_preserve_context vs. extract_media, pull_context), but some overlap exists between context preservation tools, potentially causing confusion.

    Naming Consistency3/5

    Naming is mixed: some tools follow verb_noun (get_file, set_root, update_index), while others are just verbs (health, reorganize) or use different styles (server_info). This inconsistency reduces predictability.

    Tool Count5/5

    With 10 tools, the count is well within the ideal 3-15 range and appropriate for a context management server, covering essential operations without bloat.

    Completeness4/5

    The tool set covers core context operations like preservation, extraction, search, and reorganization. Missing explicit update/delete for context items, but overall it provides a coherent workflow for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources