Skip to main content
Glama

Related Servers

Alternatives to context-crystal

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP server that lets AI agents query their own LLM call history as a branchable DAG and offload conversation context into immutable, AES-256-GCM-encrypted capsules — restorable in full or per segment, crypto-shreddable, with RAID-style replication. 12 tools, no API keys, no cloud.
      49 npm
      3
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Production-grade, autonomous Model Context Protocol (MCP) server that elevates AI models from stateless code generators into persistent, self-verifying software engineers.
      21
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP control-plane core that gives AI agents persistent project context through workspace registration, reusable skill routing, and health guardians over stdio.
      1,541 npm
      -
    • A
      license
      C
      quality
      B
      maintenance
      Enables local-first LLM orchestration with persistent memory, knowledge management, routing, swarm patterns, API probing, tests, automation planning, and plugin discovery via a stdio MCP server, using SQLite for offline storage.
      51
      62 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A robust, lightweight Model Context Protocol (MCP) server designed to empower your AI Agents with context-awareness, safe execution sandboxes, and dedicated thought logs.
      -

    TDQS

    B3.3/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target distinct lifecycle operations (init, checkpoint, task/goal transition, hydrate, archive/unarchive, prune, connect). A few overlap conceptually—checkpoint vs melt both manipulate DAG nodes, and several tools bundle multiple actions (crystal_artifact handles register/list/inspect; crystal_transient_lease handles create/clean/promote)—but descriptions keep boundaries clear enough.

    Naming Consistency5/5

    Every tool follows the crystal_<snake_case_noun/verb> pattern consistently, with readable and predictable suffixes. No camelCase or stylistic drift.

    Tool Count4/5

    17 tools is on the heavier side but justified by a rich domain (DAG lifecycle, leasing, artifacts, archival, bonding). Each tool maps to a distinct operation, though a couple could theoretically be merged.

    Completeness4/5

    Covers the full lifecycle: init, checkpoint, task/goal transitions, leases, forking, hydration, triage, archive/unarchive, melt, prune, connect, search, stats, and batch. Some minor gaps (e.g. no rename/update-metadata or explicit delete beyond prune) but core workflows are complete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues