Local Commander

Name: Local Commander
Author: netbka

by netbkaversion 0.1.4i★ –iRuns on your computer

Registry nameio.github.netbka/local-commander-mcp-agent

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools
You need to fill in: LCMCP_ROOTS

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: LCMCP_ROOTS

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

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

Fill in the empty values before running it.

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account netbka, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1396 servers in this category
Published to the registry more recently than 83% of the other 1396 servers in this category
Basic checks equal to or better than 100% of the other 1396 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Local Commander safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LCMCP_ROOTS

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 8 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker, MCPB on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

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

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

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