LetKite (dev) vs Local Commander
LetKite (dev) is an MCP server published by letkite.com. Marketplaces we read that list it: 1 (Official MCP Registry). Local Commander is an MCP server published by netbka. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  LetKite (dev) |  Local Commander |
|---|---|---|
| Official MCP Registry | Listed, marked deprecated Version: 1.7.0-rc.2 No figure published Not marked · First seen |
Listed Version: 0.1.4 Downloads/month (npm): 1 284 Downloads/week (npm): 113 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.1.4 Downloads/month (npm): 1 284 Downloads/week (npm): 113 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | LetKite (dev) | Local Commander |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-24 (worse) | 2026-10-30 (better) |
| Where it runs (differs) | Remote server (mcp.dev.letkite.com/mcp) | On your machine (local-commander-mcp-agent) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/netbka/local-commander-mcp-agent |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-19 | 2026-10-17 |
| Endpoint at the last check (differs) | Responded 29 h ago, requires authentication | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
LetKite (dev)
Run commands and manage files on your own machines. Needs a LetKite account; OAuth sign-in.
Local Commander
Files, Git, allowlisted dev commands, processes and localhost inside folders you choose.
How to run each
LetKite (dev) As a remote MCP server
claude mcp add --transport http letkite-dev https://mcp.dev.letkite.com/mcpLocal Commander As a local MCP server: npm package
claude mcp add --env "LCMCP_ROOTS=<YOUR_LCMCP_ROOTS>" --transport stdio local-commander-mcp-agent -- npx -y local-commander-mcp-agent --stdioRequires: LCMCP_ROOTS
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only LetKite (dev) has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of LetKite (dev) publish no settings it asks for, so we do not compare settings.
What it can do: LetKite (dev) · What it can do: Local Commander · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.