notify
summaryrequiredsurfacediffHashriskTierverifiedcapabilityRefcontractDeltaverifiedAgainst
io.github.lockstep-team-agentPublished by GitHub account lockstep-team-agentv0.4.0Updated Nov 4, 2026
Shared team memory for Claude Code: decisions, standards, and skills every agent session receives.
Lockstep AI's local MCP server; no sign-in required; STDIO; 20 tools.
No AI overview yet: these facts come from the registry entry and the server itself.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
The CLI for Lockstep AI: shared team memory for Claude Code.
Lockstep captures decisions from PRDs, Slack, Jira, and pull requests, gets each one approved by its owner, rolls out your team's standards and skills, and briefs every Claude Code session at start. Any MCP client can call the same tools. An opt-in check flags changes that may conflict with a binding decision.
Full setup, MCP configuration, and self-hosting (Apache-2.0, one docker compose up):
If Lockstep helps your team, star it on GitHub so other teams can find it.
Apache-2.0
Source: packages/cli/README.md at commit f613c5b
summaryrequiredsurfacediffHashriskTierverifiedcapabilityRefcontractDeltaverifiedAgainstTakes no parameters.
itemIdsscopequestionrequiredscopeurgentquestionrequiredresponserequiredquestionIdrequiredtorequiredrefstaskrequirednotetaskIdrequiredreviewAtruleTextrequiredscopeRefrequiredrationalescopeKindrequiredbaseVersionrequiredalternativesdecisionTypecapabilityRefverdictversionrequireddecisionIdrequiredproducedRepoIdproducedSurfacerequiredscopepathrequiredsurfacerequiredscoperequiredcapabilityRefrequiredbaseTakes no parameters.
Takes no parameters.
Takes no parameters.
90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npm install -g lockstep-clilockstep login # authenticatelockstep onboard # one step: wire up hooks + MCP for your agent, link this repolockstep status # check auth + config health