Local Commander MCP server
online · 100% uptimeapp.localcmd/local-commander·v1.0.2Give your AI hands on every computer you own. One chat, all your machines — even from your phone.
0 stars
Reviews
Write oneNobody has reviewed Local Commander yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Local Commander tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 553ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How Local Commander compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 1,034 ms
- faster than 10% of 30,031 servers
Install Local Commander in Claude Code, Cursor or VS Code
claude mcp add --transport http local-commander https://localcmd.app/mcp
What the publisher says
From the Local Commander repository's README, as published. We do not edit it. Read it on GitHub
Local 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@latest on 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 mcplocal-commander.
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 webYou can also build the tarball from this repository with npm pack.
Remove:
dsh plugin --profile web remove local-commander-dshAntigravity
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-pluginsOr clone the repository and run agy plugin install . Remove with agy plugin uninstall local-commander.
Kiro
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Local Commander: common questions
- Is Local Commander MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the Local Commander safety report
- How do I install Local Commander?
- It runs remotely at localcmd.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Local Commander need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Local Commander maintained?
- The last commit was 12 days ago (2026-10-23). The latest release is v1.0.2.
- Is Local Commander up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Local Commander compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,034 ms (faster than 10% of 30,031 servers). Full comparison.