Castor
Rust MCP microkernel bridging cloud planners to local sandboxed execution.
Tested on Linux
Use it
Linux x86_64
You need first
- Runtimes:
Rust >= 1.85
These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:
mkdir -p "$HOME/work" && cd "$HOME/work"Clone ApatheticMioz/Castor and cargo install --path . --locked (puts castor in ~/.cargo/bin)
npm uninstall -g mcp-castor && cd "$HOME"/work && git clone --depth 1 https://github.com/ApatheticMioz/Castor.git && cd Castor && cargo install --path . --locked
Where the README and reality differ
- README: npx -y mcp-castor install --client all (One command. Registers with every MCP client it finds.)
What worked: The npm package mcp-castor is only a Node wrapper (bin/castor.js) that spawns a native castor binary found at target/release/castor or on PATH. Without a native build, the wrapper spawns 'castor' from PATH, which is the wrapper itself, so it recurses and hangs. npx hung for 300 s (command 1) and mc…
Verified in pickfit: the commands exactly as its sandbox ran them
For the record only: they name the sandbox's home, /home/sbx.
npm uninstall -g mcp-castor && cd /home/sbx/work && git clone --depth 1 https://github.com/ApatheticMioz/Castor.git && cd Castor && cargo install --path . --locked 2>&1castor --helpcastor stats -jCheck that it works
castor --helpThe output should contain “Usage: castor [COMMAND]”.
First thing to try
castor stats -jWhat it does
- Report local usage and savings statisticsTested
- Delegate edit-and-test loops to a local modelNot tested
- Sandbox tool calls against path escapes and destructive commandsNot tested
- Auto-detect OpenAI-compatible local enginesNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- 1 of 4 features work
- Works offline
Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- dispatch a prompt to sandboxed local runtime
- read source files, PDFs and images locally
- perform structural AST code replacement
- check status and commit via git tools
- fetch web pages and convert to markdown
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- GPU: Tesla T4
- Works offline
- Checked on 16 Nov 2026
- Version 1.5.0
Differences the test machine hit
- README: Install with npx / npm install -g mcp-castor
In the test: Needs a Rust toolchain (cargo) to build the native binary; the build took about 5.5 minutes on this box. - README: castor stats [-s 24h] [-d] [-j]: numbers come from the ledger
In the test: On an empty ledger castor stats -j prints all-zero JSON keys; the README's savings figures cannot be reproduced here. - README: castor_coworker delegates the edit-and-test loop to the local engine
In the test: The MCP server shuts down when stdin closes, so a call needs stdin kept open until the task answers (sleep in the pipe). The 135M-parameter model produced incoherent text and did not create hello.txt, so the file-edit behaviour was not verified.