run_commandLABSCO SUMMARY
Shell access with three transports and a hard timeout.
The stdin parameter is what lifts this above a simple command runner — you can pipe a script or a document into a command instead of escaping it into an argument. Take the obvious precaution: anything your user can run, this can run, so keep it to a machine you are willing to have driven. The 60-second ceiling also means long builds belong elsewhere; run those directly and use this for the short commands.
What it is
A Java MCP server that executes shell commands on the host system, built as separate modules so you can pick the transport your client needs.
What you get
run_command— a requiredcommand, plus optionalworkdirandstdinto pipe input in- Structured results: stdout, stderr, a message when it fails, and an isError flag
- Three transports built from one repository: stdio for desktop clients, plus HTTP and SSE
- Commands time out after 60 seconds, so a hung process does not hold the client
- Enhanced handling for the Fish shell, and cross-platform support across macOS, Linux and Windows
- Logback logging with configurable levels and optional rolling files, set through
LOG_DIRandLOG_LEVEL - An optional GraalVM native binary if you would rather not launch a JVM per session
Requirements
Java 25 or higher, and Gradle to build from source. ./gradlew build produces a jar per transport; point Claude Desktop at the stdio one with an absolute path, or at the native executable if you compiled it.
Setup effort
Build from source — git clone https://github.com/brunorozendo/mcp-server-command.git
USE CASES
01
Letting the assistant inspect a repository
Run the command with the working directory set to the project, rather than composing a cd chain.
02
Feeding a script to an interpreter
Pass the script through stdin so quoting does not mangle it.
03
Serving a remote client
Build and run the HTTP or SSE module instead of stdio when the client is not on the same machine.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
Java 25 or later
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/brunorozendo/mcp-server-command.git
cd mcp-server-command
./gradlew buildMCP Clients
Claude Desktop — JAR
CLAUDE DESKTOP — JAR · JSON
{
"mcpServers": {
"mcp-server-command": {
"command": "java",
"args": [
"-jar",
"<YOUR_PATH_TO_STDIO_1_0>"
],
"env": {
"LOG_DIR": "/Users/<YOUR_USERNAME>/Library/Logs/Claude",
"LOG_LEVEL": "DEBUG"
}
}
}
}Claude Desktop — native binary
CLAUDE DESKTOP — NATIVE BINARY · JSON
{
"mcpServers": {
"mcp-server-command": {
"command": "<YOUR_PATH_TO_STDIO>/build/native/nativeCompile/mcp-server-command",
"env": {
"LOG_DIR": "/Users/<YOUR_USERNAME>/Library/Logs/Claude",
"LOG_LEVEL": "DEBUG"
}
}
}
}
