lockdocs MCP Server

What the code does

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

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.

const res = spawnSync(bin, process.argv.slice(2), { stdio: "inherit", windowsHide: true });

  for (const p of [path.join(root, "target", "release", exe), path.join(root, "target", "debug", exe)]) {

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    let user = env.get("NPM_CONFIG_USERCONFIG").map(PathBuf::from).or_else(|| env.home_file(".npmrc"));

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

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.

claude mcp add lockdocs -- npx -y @sylphx/lockdocs

{
  "mcpServers": {
    "lockdocs": {
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/lockdocs"
      ]
    }
  }
}

[mcp_servers.lockdocs]
command = "npx"
args = ["-y", "@sylphx/lockdocs"]

{
  "mcpServers": {
    "lockdocs": {
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/lockdocs"
      ]
    }
  }
}

{
  "servers": {
    "lockdocs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/lockdocs"
      ]
    }
  }
}