Skip to main content
Glama
lockstep-team-agent

lockstep

by lockstep-team-agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to lockstep

  • mem0-mcp by tensakulabs

    mem0-mcpofficial

    tensakulabs
    A
    license
    A
    quality
    C
    maintenance
    Self-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.
    6
    4
    MIT

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
    41
    GPL 3.0
  • Memcell by memcell-ai

    Memcellofficial

    memcell-ai
    A
    license
    Not graded
    quality
    F
    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.
    301 npm
    Apache 2.0

  • Hivemind

    Lecrupus
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables teams of AI coding agents (Claude Code, Cursor, Codex) to share persistent, time-aware graph memory and coordinate their work via MCP, so agents recall verified fixes at the moment of failure, learn procedures automatically, avoid file conflicts, claim tasks race-free, and hand off facts and decisions between sessions.
    MIT

  • 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

  • Relay

    ahirmaan
    A
    license
    A
    quality
    B
    maintenance
    Gives MCP-compatible AI assistants one shared, append-only memory stored as a graph, so facts persist across tools and sessions with their full reasoning chain. Enables finding disagreements between tools, resolving them by recording a winner, and seeing which downstream decisions become stale.
    9
    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

A3.9/5.0

Scored across 20 tools

Disambiguation4/5

Most tools have distinct resource/action targets, and descriptions explicitly cross-reference alternatives such as query vs ask, inbox vs decisions, and refresh_decision_pack vs sync_skills. Some read-oriented tools (session_briefing, inbox, decisions, query) overlap conceptually but remain distinguishable.

Naming Consistency3/5

Names are mostly lowercase snake_case and readable, but conventions are mixed: some are verb_noun (propose_decision, register_dependency), some are noun-only (inbox, decisions, consumers), and whoowns breaks the underscore pattern. The set is understandable but not predictably uniform.

Tool Count3/5

Twenty tools is heavy for a single MCP server and sits in the borderline 16-25 range. The broad collaboration domain justifies many capabilities, but the surface feels near the upper bound for easy agent selection.

Completeness3/5

Core areas such as decisions, inbox, questions, changes, dependencies, and context are covered, but lifecycle gaps remain: tasks only support delegate and complete without list/get/update, and changes or dependencies lack direct listing/removal operations. These are notable gaps that could force workarounds.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources