Local Commander

Name: Local Commander
Author: netbka

作者：netbka版本 0.1.4i★ –i在你的电脑上运行

注册名称io.github.netbka/local-commander-mcp-agent

安装

概览

作者提供的说明（英文原文）

Files, Git, allowlisted dev commands, processes and localhost inside folders you choose.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具
你需要填写：LCMCP_ROOTS

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： LCMCP_ROOTS

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

下载作者的 .mcpb 文件

链接指向作者自己的文件；我们不托管也不重新打包它。打开文件后，Claude Desktop 会进行安装。

在终端中运行这条命令

claude mcp add local-commander-agent --env LCMCP_ROOTS=your-value -- npx -y local-commander-mcp-agent --stdio your-value

运行前请先填写空着的值。

这个服务器需要在启动命令中填入值，请复制设置后自行填写。

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "local-commander-agent": {
      "command": "npx",
      "args": [
        "-y",
        "local-commander-mcp-agent",
        "--stdio",
        "your-value"
      ],
      "env": {
        "LCMCP_ROOTS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器需要在启动命令中填入值，请复制设置后自行填写。

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "local-commander-agent": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "local-commander-mcp-agent",
        "--stdio",
        "your-value"
      ],
      "env": {
        "LCMCP_ROOTS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

LCMCP_ROOTS 必填 env
Folders the server may access, separated by ; on Windows and : elsewhere

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 netbka 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 1396 个服务器的 0%
发布到注册中心的时间比此分类中其他 1396 个服务器的 83% 更新
基础检查结果等于或优于此分类中其他 1396 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Local Commander 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：LCMCP_ROOTS

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.4）于8天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker, MCPB。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT4天前更新

安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT16天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Local Commander

Your AI, on your computer.

Let Claude, Cursor, Codex or your own agent work with the files, Git and dev tools on your machine.

You choose the folders. No account, no cloud, no telemetry.

Get started · What people use it for · Why Local Commander · Questions · Technical reference

The problem

Your AI can write the code, but it can't see your project. You copy files into the chat, paste test output back, and run every command yourself. Giving it a raw terminal solves that, but then it can touch everything.

Local Commander sits in between. Your AI gets real tools for real work on your machine, inside the folders you pick, with commands you allow. You keep working in the chat you already have open.

What people use it for


Code	Run tests and builds · Fix a bug in the real repo · Review a diff before you push
Local services	Start a dev server · Check a service is up · Read its logs
Project context	Get status, recent commits and scripts in one ask · Search the codebase · Edit files in place

Try asking:

"Run the tests in my-app and tell me what fails."

"Start the dev server and check that port 3000 answers."

"Show me what changed in the repo since yesterday."

Why Local Commander

🔒 You choose the access. Your AI sees only the folders you pick. Secret files such as .env and private keys are blocked by default.

🧰 Real tools, not a raw shell. Commands run from an allowlist (Git, Node, npm, Python and similar) with separate arguments. There is no free-form shell string to inject into.

⚡ Parallel work without collisions. Independent commands run side by side. Long-running processes such as dev servers keep running while your AI checks their output.

🏠 Stays on your machine. The server runs locally and talks only to the AI client that started it. No account, no telemetry, and the audit log is off unless you turn it on.

🔌 Works with the AI you already have. Claude Desktop, Claude Code, Cursor, Codex, ChatGPT over a tunnel, or anything that speaks MCP.

Get started

Pick the way that fits you. Each takes a couple of minutes.

You use	Do this
Claude Desktop	Download the `.mcpb` file from the latest release and open it. Choose your folders. No Node.js needed.
Claude Desktop or Cursor, with Node.js 20+	`npx -y local-commander-mcp-agent setup --root /path/to/your/projects --client all` and restart the app.
Claude Code	`claude mcp add local-commander -- npx -y local-commander-mcp-agent --stdio /path/to/your/projects`
Docker	Mount your projects into `ghcr.io/netbka/local-commander-mcp-agent`. See Docker.
Any other MCP client	Run `npx -y local-commander-mcp-agent --stdio /path/to/your/projects`. See npx.

Before you install

What can my AI touch?

Only the folders you choose, and only through Local Commander's tools: reading and editing files, Git inspection, allowlisted commands, dev processes and requests to localhost. You can change the command list in the config file.

Is it a sandbox?

No. File tools are limited to your folders, but an allowed program such as node or python runs with your account's permissions and can read what you can read. For hard isolation, use the Docker image, a separate low-privilege account or a VM.

Does my data go anywhere?

No. The server runs on your computer and talks only to the AI client that started it. There is no telemetry. What your AI client sends to its own provider is between you and that provider.

Can I remove it?

Yes. npx -y local-commander-mcp-agent setup --remove takes it out of Claude Desktop and Cursor and keeps a backup of the previous config. In Claude Desktop you can also disable or remove the extension.

What about several computers or a team?

This open-source edition runs one computer at a time. The hosted service at localcmd.app connects ChatGPT, Claude or your own agent to all your computers at once, runs tasks on several machines in parallel and shows which computer ran what. It is a separate product and is not needed for this one.

Technical reference

Tools
Install options: setup · npx · Docker · Node.js · HTTP and ChatGPT
Security model
Configuration
Development

Tools

Tool	Purpose
`project_snapshot`	One-call repo context: status, diff stat, recent commits, package scripts, managed processes
`fs_read`, `fs_list`, `fs_search`	Bounded reads, listings and text search inside allowed roots
`fs_write`, `fs_replace`	Create/replace a file, or an exact targeted replacement
`git_status`, `git_diff`, `git_log`	Compact Git inspection
`command_run`, `parallel_command_run`	One or several allowlisted executables with separate arguments
`process_start`, `process_list`, `process_output`, `process_kill`	Long-running dev processes
`scheduler_status`	Active/queued work and resource locks
`localhost_request`	Bounded HTTP to allowlisted local hosts only

Install options

One-command setup

Requirements: Node.js 20+.

npx -y local-commander-mcp-agent setup --root /path/to/your/projects --client all

This adds a local-commander entry to the Claude Desktop and/or Cursor MCP configuration, keeping a timestamped backup of the previous file. Repeat --root for more folders, use --client claude-desktop or --client cursor for one client, --dry-run to preview, and setup --remove to take the entry out again. Restart the client afterwards.

npx

Requirements: Node.js 20+. Folders the server may access follow --stdio:

"mcpServers": { "local-commander": { "command": "npx", "args": ["-y", "local-commander-mcp-agent", "--stdio", "/path/to/your/projects"] } } }

On Windows some clients need "command": "cmd" with "args": ["/c", "npx", "-y", ...]; setup writes that form for you.

LCMCP_ROOTS still works instead of folder arguments. In stdio mode local state is kept in ~/.local-commander-mcp-agent unless LCMCP_OAUTH_STATE_PATH is set.

On Windows use ; between several roots and paths such as C:\\Users\\you\\source\\repos. The package includes the small Windows file-read helper, so nothing is compiled at install time.

Docker

The container is the sandbox: the server only sees the folders you mount under /workspace. The image is published as ghcr.io/netbka/local-commander-mcp-agent (tags latest and each version). To build it yourself: docker build -t local-commander-mcp-agent .

MCP client configuration (Claude Desktop, Cursor, Claude Code, Codex and others):

"mcpServers": { "local-commander": { "command": "docker", "args": [ "run", "-i", "--rm", "-v", "/path/to/your/projects:/workspace/projects", "ghcr.io/netbka/local-commander-mcp-agent" ] } } }

On Windows use a path such as C:\\Users\\you\\source\\repos:/workspace/repos. The image contains Node.js 22, Git and Python 3. Add tools by extending the image.

HTTP instead of stdio:

docker run --rm -p 127.0.0.1:17321:17321 \

-e LCMCP_TOKEN=generate-a-long-random-token \ -v /path/to/your/projects:/workspace/projects \ ghcr.io/netbka/local-commander-mcp-agent --http

The image defaults to --stdio; any other argument after the image name (here --http) replaces it and starts the HTTP server. The endpoint is http://127.0.0.1:17321/mcp with Authorization: Bearer . Publish the port on 127.0.0.1 only.

Node.js

Requirements: Node.js 20+.

npm install

npm run build

"mcpServers": { "local-commander": { "command": "node", "args": ["/path/to/local-commander-mcp-agent/dist/index.js", "--stdio", "/path/to/your/projects"] } } }

In stdio mode stdout carries only MCP messages and logs go to stderr. HTTP authentication settings do not apply, because only the client that started the process can talk to it.

On Windows the build also compiles a small file-read helper (release/personal/OwnerBridge.exe) with the .NET Framework compiler that ships with Windows. Other platforms use the Node reader.

HTTP and ChatGPT

cp local-commander.config.example.json local-commander.config.json   # set "roots"

LCMCP_AUTH_MODE=oauth LCMCP_PUBLIC_BASE_URL=https://your-tunnel.example.com npm start

When the client starts authorization, a one-time approval code is printed in the local terminal. Bearer mode (LCMCP_AUTH_MODE=bearer, LCMCP_TOKEN=...) is available for local clients.

Security model

Direct file operations are constrained to the configured roots; existing paths are resolved with realpath, so symlinks cannot escape a root.
Common secret files (.env, private keys, credential files) are blocked by default.
command_run takes an executable and an argument array, never a shell string. Executables are allowlisted and resolved from absolute PATH directories only.
Command time and output are capped; HTTP is limited to localhost and redirects are not followed.
Child processes are not OS-sandboxed outside Docker: an allowed interpreter can read anything the account can read. For hard containment use the Docker image, a separate low-privilege account or a VM.

Configuration

Variable	Meaning
`LCMCP_TRANSPORT`	`stdio` to serve over stdio (same as `--stdio`)
`LCMCP_ROOTS`	Allowed roots separated by the OS path delimiter (`;` on Windows, `:` elsewhere)
`LCMCP_CONFIG`	Config file path (default `local-commander.config.json` in the working directory)
`LCMCP_HOST`, `LCMCP_PORT`, `LCMCP_MCP_PATH`	HTTP bind and path
`LCMCP_AUTH_MODE`	HTTP only: `oauth`, `bearer` or `none`
`LCMCP_TOKEN`	Token for bearer mode
`LCMCP_PUBLIC_BASE_URL`	Public HTTPS origin used as OAuth issuer/resource
`LCMCP_OAUTH_STATE_PATH`	OAuth and local state file path
`LCMCP_AUDIT_MODE`	`off` (default), `minimal`, `diagnostic` or `full` (full requires `LCMCP_AUDIT_RECOVERY_KEY`)

The config file can also set the command allowlist (shell.allowedCommands), size limits and localhost hosts; see local-commander.config.example.json.

Development

npm run typecheck

npm test npm run build

MIT licensed · Report an issue · Hosted multi-computer service: localcmd.app

Local Commander

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“开发者工具”中的其他服务器比较i

常见问题

替代选择

GitHub

Desktop Commander

Cloudflare MCP

作者的 README

Local Commander

Your AI, on your computer.

The problem

What people use it for

Why Local Commander

Get started

Before you install

Technical reference

Tools

Install options

One-command setup

npx

Docker

Node.js

HTTP and ChatGPT

Security model

Configuration

Development