Local Commander

app.localcmdPublished by localcmd.appOfficial publisherv1.0.2Updated Oct 27, 2026

Give your AI hands on every computer you own. One chat, all your machines — even from your phone.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Remote MCP server that lets an AI assistant run commands, edit files and check services on your own Windows computers from one chat.

What you can do
  • Run commands and scripts on approved computers
  • Change system settings and edit files on those machines
  • Check local services and report how each request ended
  • List the computers paired to your account and pick an approved project to work on
  • Stop running work or switch a computer off from the localcmd.app workspace
When to use it
Useful when you want a chat assistant to operate your own Windows machine or several machines remotely, for example running scripts, editing files or checking services, including from a phone. It suits users who accept broad local access in exchange for convenience and who want per-run visibility of which computer did what.
Requirements
A Local Commander account at localcmd.app with OAuth 2.0 sign-in. A Windows 11 x64 computer with Node.js 20 or later running the paired agent (npx local-commander-agent@latest), with full access or selected folders chosen. The computer must be online for work and for reading results. Some client bundles need Node.js 22.19 or later or LM Studio 0.3.17 or later.
Before you install
Once a computer is approved, the assistant can do what your Windows account can do, like you at the keyboard, including running commands, changing settings and editing files. Limit it to certain folders, block commands and stop work from the site. Requests and results pass through localcmd.app and go back to the AI. Sign-in happens on localcmd.app, so the client never sees your password.

Installation

In SourceWeft

  1. Open Local Commander in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.localcmd%2Flocal-commander/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "local-commander": {
      "type": "http",
      "url": "https://localcmd.app/mcp"
    }
  }
}

README

Local Commander for Cursor, DeepSeek Harness, Antigravity, Kiro and LM Studio

[M8ven Score]

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

  1. Install the plugin, or add this to ~/.cursor/mcp.json:

    json
    {  "mcpServers": {    "local-commander": { "url": "https://localcmd.app/mcp" }  }}

  2. Cursor opens localcmd.app to sign in and approve access (OAuth 2.0). Sign-in happens on localcmd.app; Cursor never sees your password.

  3. 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:

sh
dsh plugin --profile web add ./local-commander-dsh-1.0.0.tgzdsh web

You can also build the tarball from this repository with npm pack.

Remove:

sh
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:

sh
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.

  1. In LM Studio, open the Program tab in the right sidebar, choose Install > Edit mcp.json, and add:

    json
    {  "mcpServers": {    "local-commander": {      "command": "npx",      "args": ["-y", "[email protected]", "https://localcmd.app/mcp"]    }  }}

    Or paste this link into your browser's address bar on that computer, and LM Studio adds the same entry:

    text
    lmstudio://add_mcp?name=local-commander&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIm1jcC1yZW1vdGVAMC4xNS4xIiwiaHR0cHM6Ly9sb2NhbGNtZC5hcHAvbWNwIl19

  2. In a chat, turn on mcp/local-commander and choose a model that supports tool calls. On first use your browser opens localcmd.app to sign in and approve access.

  3. 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: [email protected] (https://localcmd.app/support).

License

MIT, for the files in this repository.

Source: README.md at commit b84d3c0

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.0.2LatestOct 23, 2026
  2. v1.0.1Oct 20, 2026
  3. v1.0.0Oct 18, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Localcmd integrations

Local Commander

Published by GitHub account netbka

Local MCP server that gives an AI assistant scoped access to chosen folders on your machine: files, Git, allowlisted dev commands, processes and localhost.

STDIODesktop only
Cloud & InfrastructureNot validated · the server did not startNov 6, 2026