Skip to main content
Glama
ericmaddox

Calyx MCP

by ericmaddox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Calyx MCP

No user-submitted related servers found.

    Related Servers

    • MegaBrain

      dougrn
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants to share persistent local memory across sessions and agents, so rules, mandatory specs, verified code snippets, and past mistakes are automatically surfaced before code is generated. It also lets agents log repeated failures as recurrence-counted 'vaccines', preventing the same errors from recurring across Claude, VS Code agents, and local LLMs.
      7
      1
      MIT

    • KOPENG

      djy89
      F
      license
      Not graded
      quality
      C
      maintenance
      Persistent, self-curating memory for coding agents. It enables local, zero-cost context recall through MCP tools with hybrid retrieval and autonomous consolidation.
      -

    • io.github.cdnsteve/sugar

      Sebastien94506
      F
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents persistent, local-first memory so they can store, semantically search, and recall decisions, preferences, error patterns, and cross-project guidelines directly during a session. It also optionally queues tasks for autonomous execution against that same memory.
      -

    • memory-engine

      top777
      A
      license
      B
      quality
      C
      maintenance
      Enables programming agents to capture errors and conversation signals, reflect on root causes, consolidate reusable skills, and retrieve relevant context for future tasks, providing a self-learning memory loop.
      15
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct role: querying memory, checking code reflexes, inspecting state, learning outcomes, and resetting. The only mild overlap is between query_associative_memory and check_code_reflex, since both access stored patterns, but their purposes are clearly separated by general search versus instant classification.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: query_, check_, inspect_, remember_, and reset_. The naming clearly communicates the action and target for every tool.

    Tool Count5/5

    Five tools is well-scoped for a memory system server. Each tool covers a necessary operation without redundancy or bloat.

    Completeness5/5

    The tool set covers the full lifecycle of associative memory: querying, fast checking, inspecting state, learning from outcomes, and resetting/pruning. No obvious dead ends or missing critical operations exist for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources