Kilnshell

[Kilnshell]

Your whole machine, for AI agents. Without the wait.

Terminal, files, code search, long-running processes, PDF, Excel and Word, over MCP.
Everything Desktop Commander does, up to 100x faster per call, with no telemetry and nothing injected into your agent's context.

[CI] [MCP] [No telemetry] [Node 22.12+] [MIT]

Benchmark

[Kilnshell vs Desktop Commander, median time per tool call]

MacBook Pro (Apple Silicon), macOS, zsh with a typical developer profile (Homebrew and nvm), Node 25, median of 9 calls over real MCP stdio, telemetry turned off in the Desktop Commander config. The command speed-up depends on your shell profile: the heavier it is, the bigger the gain. On a bare Linux machine with an empty profile, commands are about 3x faster and file tools 3x to 6x faster.

Reproduce it on your machine:

git clone https://github.com/Soflutionltd/kilnshell && cd kilnshellnpm installnpm run bench        # installs Desktop Commander 0.3.1 next to it, runs both, redraws the chart

What changed, and why it is faster

Kilnshell started as a clone of Desktop Commander 0.3.1, profiled call by call.

1. The shell profile is read once, not on every command. Desktop Commander starts every command as zsh -l -c ..., so a profile that loads nvm, pyenv or Homebrew costs 0.5 to 1 s per command. Kilnshell runs the login profile once at start-up, keeps the environment it produces (same PATH, same variables) and starts each command with zsh -c. Set DESKTOP_COMMANDER_LOGIN_ENV_CACHE=0 to get a fresh login shell every time.
2. No process is spawned behind your back on every call. Telemetry rebuilt its system report for each tool call, which ran python3 --version synchronously and froze the server for 10 to 25 ms, even with telemetry turned off. System facts are now computed once.
3. Line counting uses native string scanning. Reading, editing and inspecting a file counted its lines character by character; the new count gives identical results (checked on 200,000 random inputs) about 11x faster on large files.
4. No debug chatter. Every call used to push two to four [FEEDBACK DEBUG] log notifications to the client.
5. Fewer round trips. For an agent, each tool call costs a full round trip, often far more than the command itself. Kilnshell adds:
   • batch: several tool calls (commands, reads, edits, searches) in one request, results numbered in order;
   • read_process_output with wait_for_exit: true: waits for the process to end and returns all its output at once, instead of polling;
   • start_search with wait: true: returns every result in one call, instead of start_search then get_more_search_results;
   • wait_for: waits until a port accepts connections, a file exists, a URL answers or a process exits, instead of sleep loops.
6. Works at full speed inside Claude Desktop. Claude Desktop runs extensions in its own Node; the environment is captured with env -0, so the profile cache works there too, and Claude's ELECTRON_* variables never reach your commands.

What was removed

Everything else is the same code: the same tools, the same arguments, the same config file (~/.claude-server-commander/config.json), so Kilnshell is a drop-in replacement. The new tools and options are additions only.

Install

Claude Desktop: download kilnshell.mcpb and double-click it (or Settings > Extensions > Advanced settings > Install Extension). The Kilnshell icon then shows next to every tool call.

Claude Code: /plugin install kilnshell --marketplace Soflutionltd/kilnshell

Also listed in the official MCP Registry as com.soflution/kilnshell.

Cursor or any MCP client:

{  "mcpServers": {    "kilnshell": {      "command": "npx",      "args": ["-y", "kilnshell@latest"]    }  }}

Or from a local clone, which starts faster than npx:

git clone https://github.com/Soflutionltd/kilnshell && cd kilnshell && npm install

{ "mcpServers": { "kilnshell": { "command": "node", "args": ["/absolute/path/to/kilnshell/bin/supervise.cjs"] } } }

Automatic updates

Every install below keeps itself up to date, without restarting Claude or Cursor. The MCP client talks to a small supervisor (bin/supervise.cjs) that stays connected while the server runs behind it. At start-up and every 6 hours it asks npm for the latest kilnshell, installs it in the background in ~/.soflution/mcp/kilnshell/, and switches over as soon as no request is in flight (the client is told the tool list may have changed). A version that fails to start is rolled back at once and never picked again on that machine. npm checks the integrity of every download, and releases are published from GitHub Actions with provenance.

The only network call is that version check to registry.npmjs.org; nothing about your machine or your use is sent. Turn it off with NO_UPDATE_NOTIFIER=1 (or SOFLUTION_AUTO_UPDATE=0). Started directly with node dist/..., kilnshell does not update itself and only mentions a newer version in its first tool result.

Tools

Security controls are unchanged: allowedDirectories, blockedCommands, file read and write line limits, all in the config file.

Develop

npm installnpm run buildnpm test            # the full upstream test suite (takes several minutes)npm run bench       # Kilnshell vs Desktop Commander on this machine

Credits and license

Kilnshell is built on Desktop Commander by Eduard Ruzga and the Desktop Commander contributors, released under the MIT license. Their full history is kept in this repository. Kilnshell is an independent project, not affiliated with or endorsed by them.

MIT, © 2024-2025 Eduard Ruzga and Desktop Commander Contributors, © 2026 Soflution Ltd. See LICENSE.

En français

Kilnshell est un serveur MCP qui donne à un agent IA l'accès à votre machine : terminal, fichiers, recherche dans le code, processus, PDF, Excel et Word. C'est un clone de Desktop Commander, optimisé appel par appel : jusqu'à 100 fois plus rapide sur un Mac de développeur, sans aucune télémétrie, et sans texte publicitaire injecté dans les réponses données à l'agent. Il se remplace d'une ligne dans la configuration de Claude.