Overview
Features
run_command interface
Expose a single MCP command to execute arbitrary shell commands and return STDOUT and STDERR.
stdin input support
Optional stdin parameter allows feeding code or input to shells (bash, zsh, fish, python) and creating files via redirection.
STDIO transport
Implemented as an STDIO-based MCP server, enabling simple, streaming bidirectional communication.
HTTP/OpenAPI bridge
OpenAPI-compatible HTTP endpoint through mcpo for integration with HTTP clients and Open-WebUI.
Logging and verbosity
Logs can be enabled for verbose output; logs are written to STDERR for Claude Desktop compatibility.
Open-WebUI compatibility
Works with Open-WebUI ecosystems via the mcpo bridge.
Developer tooling
Development workflow includes npm install, npm run build, and optional watch for auto-rebuild; inspector debugging via npm run inspector.
Security and permissions guidance
Permissions are determined by the user running the server; avoid using sudo to minimize risk.
Who Is This For?
- LLMs / AI agents:Request command execution and receive stdout/stderr outputs for task automation.
- Developers / Integrators:Configure and expose the MCP server in Claude Desktop or Groq Desktop, or bridge via HTTP/OpenAPI.
- Model researchers / engineers:Test and evaluate tool usage with local models (e.g., Ollama/OpenHands-LM) to drive tool use.
- End users of Claude Desktop:Review/approve commands before execution and manage permissions (no sudo).




