mcpbeat Sign in

Lockstep MCP Server

by lockstep-team-agent Your server? Claim it
local only

Lockstep runs on your own machine — the client starts it, so there is no endpoint to ping. 70 installs a week from npm. Last commit 25 Oct 2026.

Decision memory for AI coding agents: captures decisions once, briefs every agent before it acts.

Installs per day peak 199 · avg 35 · -78% w/w
a month agotoday
70
Installs / week
npm · lockstep-cli
11
Stars
0 open issues
25 Oct 2026
Last commit
5 releases in 90 days
Apache-2.0
License
TypeScript

What the code does

We read the source, 1 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable packages/core/src/db/migrate.ts:29
      const p = path.join(sqlDir, file);
Builds a database query by concatenation packages/core/src/concepts/views.ts:356
              ${like ? sql`AND (d.scope_ref ILIKE ${like} OR EXISTS (SELECT 1 FROM decision_versions v WHERE v.decision_id = d.id AND v.rule_text ILIKE ${like}))` : sql``}
Touches key and credential files packages/core/src/standards/packages.ts:18
const SECRET_LIKE = /(^|\/)(\.env(\..*)?|\.npmrc|\.pypirc|id_[a-z0-9]+|credentials(\.json)?|.*\.(pem|key|p12|pfx|keystore))$/i;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add lockstep -- npx -y lockstep-cli
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "lockstep": {
      "command": "npx",
      "args": [
        "-y",
        "lockstep-cli"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.lockstep]
command = "npx"
args = ["-y", "lockstep-cli"]
.cursor/mcp.json
{
  "mcpServers": {
    "lockstep": {
      "command": "npx",
      "args": [
        "-y",
        "lockstep-cli"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "lockstep": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "lockstep-cli"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: LOCKSTEP_VENDOR (Agent vendor label used for session registration (e.g. claude-code, cursor). Optional; defaults to unknown).

Alternatives to Lockstep

same job, measured the same way
Peon Mem
by vineetv2

Local-first memory brain for AI coding agents: hooks capture sessions, beliefs injected per prompt.

90 installs/wk local only
Robrain
by adelinamart

Self-hosted decision memory for AI coding agents; warns before re-proposing a rejected approach.

922 installs/wk local only
EchoVault Memory
by go-ports

Local-first memory for coding agents; stores decisions, bugs, and context across sessions.

local only
CommitLore
by monglong0214

Git-native decision memory for coding agents: only the decisions still in force for the edited path

local only
Project Memory MCP
by kaaustubh

Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.

68 installs/wk local only
K
Knowledge MCP
by fulminate-io

Persistent memory graph for coding agents: hypotheses, evidence, and decisions survive sessions.

local only
Todox
by beydemirfurkan

Memory for coding agents: the decisions, the dead ends, and where the last session stopped.

answering
Projectmem
by riponcm

Coding agent memory — one local MCP server for every project. Warns before repeating failed fixes.

1 327 installs/wk local only

Lockstep — questions

Answers built from our own checks of this server.

Why is there no uptime for Lockstep?
Lockstep runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package lockstep-cli was installed 70 times last week.
How do I connect Lockstep?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls lockstep-cli straight from npm; nothing to host, nothing to sign up for.
How many people use Lockstep?
The npm package lockstep-cli was installed 70 times in the last week. Week over week that is -78%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Lockstep open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 11 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.