commands

commands

Run commands and scripts. Just like in a terminal.

208
Stars
33
Forks
2
Releases

Overview

This MCP server implements a focused tool for LLM-driven automation: the run_command interface. It executes arbitrary shell commands on the host process and returns both STDOUT and STDERR as text. An optional stdin parameter lets the LLM feed code or input to interactive shells (e.g., bash, zsh, fish, python) and even perform file operations (for example via cat >> foo/bar.txt). The server is designed to be used with Claude Desktop and Groq Desktop, acting as a bridge between the LLM and the host environment while keeping permissions under the user’s control (no sudo). It uses the STDIO transport for command communication, and can be exposed over HTTP via mcpo to provide an OpenAPI-compatible web server interface, compatible with Open-WebUI ecosystems. Development workflows are npm-based (npm install, npm run build, npm run watch for auto-rebuild). Logging is available and can be increased with verbose mode; logs are written to STDERR for compatibility with Claude Desktop routing. Debugging can be facilitated through the MCP Inspector. The README also provides configuration guidance for local deployment and HTTP bridging.

Details

Owner
g0t4
Language
TypeScript
License
MIT License
Updated
2025-12-07

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.

Audience

LLMs / AI agentsRequest command execution and receive stdout/stderr outputs for task automation.
Developers / IntegratorsConfigure and expose the MCP server in Claude Desktop or Groq Desktop, or bridge via HTTP/OpenAPI.
Model researchers / engineersTest and evaluate tool usage with local models (e.g., Ollama/OpenHands-LM) to drive tool use.
End users of Claude DesktopReview/approve commands before execution and manage permissions (no sudo).

Tags

command-executionSTDIOOpenAPIHTTPClaude-DesktopGroq-DesktopLLMsOpen-WebUIloggingdebugging