Skip to main content
Glama
lockstep-team-agent

lockstep

by lockstep-team-agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to lockstep

No user-submitted related servers found.

    Related Servers

    • Kage

      kage-core
      A
      license
      A
      quality
      A
      maintenance
      Shared, code-grounded memory for developers and their coding agents. Capture a learning once and the whole team plus every agent recalls it; memory is grounded in your code and stored as git-tracked JSON reviewed in PRs, with citations validated on write and stale memory withheld from recall. Works with any MCP client.
      11
      33
      GPL 3.0
    • Memcell by memcell-ai

      Memcellofficial

      memcell-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Living memory for AI coding agents (Claude Code, Cursor, Copilot, Codex). Cross-vendor persistent memory, decision recall, and outcome calibration via MCP and hooks.
      780 npm
      Apache 2.0

    • robrain

      adelinamart
      A
      license
      A
      quality
      A
      maintenance
      Self-hosted decision memory for AI coding agents. Captures decisions with the alternatives you rejected, and warns before an agent re-proposes a rejected approach.
      4
      81
      Apache 2.0

    • Tages

      ryantlee25-droid
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to maintain persistent, cross-session memory of codebase architecture, naming conventions, and decisions through MCP tools. Eliminates repetitive project re-explanation by automatically injecting stored context into every session with local-first SQLite storage and optional team sharing capabilities.
      4
      MIT

    • agenthelm

      jayasukuv11-beep
      A
      license
      A
      quality
      C
      maintenance
      Shared, versioned memory and governance control plane for AI coding agents. Compiler pipeline resolves architectural decision conflicts across Claude Code, Cursor, and custom agent fleets.
      3
      6
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.5/5.0

    Scored across 17 tools

    Disambiguation2/5

    With no descriptions, tools like 'inbox', 'ack_inbox', 'notify', 'query', and 'ask' have unclear boundaries and could easily be confused. Several names suggest overlapping actions (e.g., 'query' vs 'ask', 'decisions' vs 'propose_decision'), making it hard for an agent to reliably select the right one.

    Naming Consistency2/5

    Naming conventions are mixed: single-word verbs (inbox, notify, query, ask) appear alongside verb_noun compounds (ack_inbox, propose_decision, refresh_decision_pack) and bare nouns (decisions, consumers). The pattern is inconsistent and does not follow a uniform grammatical structure, though some names like 'get_product_context' are descriptive.

    Tool Count3/5

    17 tools is on the heavy side of the typical range (3-15) and feels borderline for a workflow-focused server. Without descriptions, it is plausible some tools could be consolidated, but the count is not extreme. It remains within a workable range.

    Completeness3/5

    The names suggest a workflow covering inbox management, decisions, notifications, and context, but obvious lifecycle operations are missing or unclear, such as rejecting a decision, updating a decision, or removing dependencies. There are no dead ends apparent, but the lack of descriptions makes it hard to confirm whether the surface fully covers the intended domain.

    Resources