Local Commander MCP server
Commit Nov 8, 2026Allows AI clients to run commands, edit files, and manage settings across multiple remote computers from a single chat interface.
Also known as netbka/local-commander-plugins, local-commander-plugins
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.2
- Last commit
- Nov 8, 2026
- License
- MIT
What is Local Commander MCP?
Local Commander allows AI clients to run commands, edit files, and manage settings across multiple remote computers from a single chat interface.
Summary generated from the project's README
About Local Commander MCP server
Local Commander connects AI clients to your remote Windows 11 computers through a centralized service. By using the localcmd.app endpoint, developers can grant AI agents the ability to run scripts, edit files, manage settings, and check local services across multiple machines from a single chat interface. This setup requires a Local Commander account and a running agent on each target computer using Node.js 20 or later.
The system supports various AI environments including Cursor, DeepSeek Harness, Antigravity, Kiro, and LM Studio. It utilizes OAuth 2.0 for secure sign-in, ensuring that your passwords remain private. You maintain control by limiting the agent to specific folders, blocking certain commands, or stopping active work through the web workspace. Every action is logged, showing exactly which computer executed a specific request.
What you can do with it
- 1Manage multiple remote machinesAsk your AI client to list all your connected computers and start working on a specific project.
- 2Execute system commands and scriptsDirect the AI to run terminal commands or scripts on your Windows 11 hardware.
- 3Control file system accessRestrict the AI agent to only interact with specific directories on your computer.
Written from the project's README. Every use case is checked against a quote from it.
How to install Local Commander MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Local Commander MCP in Claude Code
$ claude mcp add --transport http local-commander-plugins https://localcmd.app/mcpInstall Local Commander MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"local-commander-plugins": {
"url": "https://localcmd.app/mcp"
}
}
}Install Local Commander MCP in VS Code
.vscode/mcp.json
{
"servers": {
"local-commander-plugins": {
"type": "http",
"url": "https://localcmd.app/mcp"
}
}
}Install Local Commander MCP in VS Code CLI
$ code --add-mcp '{"name":"local-commander-plugins","type":"http","url":"https://localcmd.app/mcp"}'Install Local Commander MCP in Codex
$ codex mcp add local-commander-plugins --url https://localcmd.app/mcpInstall Local Commander MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.local-commander-plugins] url = "https://localcmd.app/mcp"
Install Local Commander MCP in Gemini CLI
$ gemini mcp add -s user --transport http local-commander-plugins https://localcmd.app/mcpInstall Local Commander MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"local-commander-plugins": {
"url": "https://localcmd.app/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablenetbka/local-commander-plugins is public and reachablegithub.com/netbka/local-commander-plugins ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-08github.com/netbka/local-commander-plugins ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubLocal Commander for Cursor, DeepSeek Harness, Antigravity, Kiro and LM Studio
Connects Cursor, DeepSeek Harness, Antigravity, Kiro and LM Studio to Local Commander at https://localcmd.app/mcp. Your AI gets hands on every computer you own: it can run commands and scripts, change settings, edit files and check local services on any of them, from one chat. Your workspace at localcmd.app shows which computer ran each request and how it ended.
This repository holds configuration only: a Cursor plugin, a DeepSeek Harness bundle, an Antigravity plugin, a Kiro Power and LM Studio settings. The service runs at localcmd.app.
Requirements
- A Local Commander account at localcmd.app.
- A Windows 11 x64 computer with Node.js 20 or later and the paired agent: run
npx local-commander-agent@lateston it, then choose full access or selected folders. - The computer must be online for work and for reading results.
Once you approve a computer and connect your AI, it can do what your Windows account can do, just like you at the keyboard. You can limit it to certain folders, block commands, stop running work, or switch a computer off from the site at any time. Every run shows which computer did it. Whatever the AI asks for goes back to the AI.
Cursor
-
Install the plugin, or add this to
~/.cursor/mcp.json:{ "mcpServers": { "local-commander": { "url": "https://localcmd.app/mcp" } } } -
Cursor opens localcmd.app to sign in and approve access (OAuth 2.0). Sign-in happens on localcmd.app; Cursor never sees your password.
-
Ask the agent to list your computers, then work on an approved project.
Troubleshooting:
- The agent reports no computers: start the agent on the Windows computer and check that it shows as online at localcmd.app.
- Sign-in loops or fails: open Output, choose "MCP Logs", and check the OAuth error; then remove and re-add the server.
- A result is unknown: the computer dropped during the task. The work is not re-run automatically; check the computer and ask again.
DeepSeek Harness
A configuration-only DeepSeek Harness bundle. The tools appear as mcp__local-commander__<tool>.
The harness MCP client sends static headers only, so the bundle starts mcp-remote over stdio. On first use it opens localcmd.app in your browser to sign in and approve access (OAuth 2.0), then keeps the token refreshed. In your localcmd.app workspace these requests show the client name "MCP CLI Proxy", the name mcp-remote registers.
DeepSeek Harness asks for Node.js 22.19 or later on the machine where you chat.
Install: download local-commander-dsh-1.0.0.tgz from the latest release, then run:
dsh plugin --profile web add ./local-commander-dsh-1.0.0.tgz
dsh web
You can also build the tarball from this repository with npm pack.
Remove:
dsh plugin --profile web remove local-commander-dsh
Antigravity
This repository is also an Antigravity plugin (.antigravity-plugin/plugin.json plus mcp_config.json). Like the DeepSeek Harness bundle, it starts mcp-remote over stdio, which opens localcmd.app in your browser to sign in and approve access (OAuth 2.0) and keeps the token refreshed. Requests show the client name "MCP CLI Proxy" in your localcmd.app workspace.
Install:
agy plugin install https://github.com/netbka/local-commander-plugins
Or clone the repository and run agy plugin install <folder>. Remove with agy plugin uninstall local-commander.
Kiro
The kiro-power/ folder is a Kiro Power in the Agent Plugins format (plugin.json and mcp.json). It points Kiro at the remote server https://localcmd.app/mcp (Streamable HTTP), which uses OAuth 2.0 sign-in at localcmd.app.
Install: in Kiro, open the Powers panel, choose Add Custom Power, then Import power from GitHub, and enter https://github.com/netbka/local-commander-plugins/tree/main/kiro-power.
LM Studio
LM Studio 0.3.17 or later runs MCP servers listed in its mcp.json. Like the DeepSeek Harness bundle, the entry starts mcp-remote over stdio, which opens localcmd.app in your browser to sign in and approve access (OAuth 2.0) and keeps the token refreshed. Requests show the client name "MCP CLI Proxy" in your localcmd.app workspace. The computer running LM Studio needs Node.js 20 or later.
-
In LM Studio, open the Program tab in the right sidebar, choose Install > Edit mcp.json, and add:
{ "mcpServers": { "local-commander": { "command": "npx", "args": ["-y", "mcp-remote@0.15.1", "https://localcmd.app/mcp"] } } }Or paste this link into your browser's address bar on that computer, and LM Studio adds the same entry:
lmstudio://add_mcp?name=local-commander&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIm1jcC1yZW1vdGVAMC4xNS4xIiwiaHR0cHM6Ly9sb2NhbGNtZC5hcHAvbWNwIl19 -
In a chat, turn on
mcp/local-commanderand choose a model that supports tool calls. On first use your browser opens localcmd.app to sign in and approve access. -
Ask the model to list your computers, then work on an approved project.
Links
Privacy: https://localcmd.app/privacy. Terms: https://localcmd.app/terms. Support: peter.mamrukov@localcmd.app (https://localcmd.app/support).
License
MIT, for the files in this repository.
Local Commander MCP questions
How do I add Local Commander MCP to Claude Code?
Run claude mcp add --transport http local-commander-plugins https://localcmd.app/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Local Commander MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can the AI do on my computers?
The AI can run commands and scripts, change settings, edit files, and check local services on any approved computer.
How do I secure my computer when using Local Commander?
You can limit the AI to specific folders, block certain commands, stop running work, or switch a computer off from the website at any time.
What are the system requirements for the Windows agent?
You need a Windows 11 x64 computer with Node.js 20 or later and the paired agent running.
Does the AI see my passwords during sign-in?
No, sign-in happens on the localcmd.app website via OAuth 2.0, so the AI client never sees your password.