MCP server for managing interactive CLI binary processes
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"executor-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Executor MCP Server An MCP (Model Context Protocol) server for managing interactive CLI binary processes. This server enables AI assistants to launch persistent binary processes, send stdin commands, and read stdout/stderr responses over time. ## Features - **Persistent Process Management**: Launch binaries that run in the background - **Interactive I/O**: Send commands to stdin and read from stdout/stderr - **Output Buffering**: Keeps last 1000 lines in memory per stream - **Comprehensive Logging**: All I/O is logged to timestamped files - **Multiple Process Support**: Manage multiple binaries simultaneously - **Real-time Output**: Background tasks continuously capture output ## Important Note This MCP server uses **stdio transport** for communication with MCP clients (like Claude Desktop). This is separate from the stdin/stdout of the binaries being managed. The server manages the stdin/stdout of your target binaries independently. ## Installation ### From Source ```bash # Clone or navigate to the directory cd skills/mcp-builder/runner # Install in development mode pip install -e . # Or install from the directory pip install . ``` ### Dependencies - Python >= 3.10 - mcp >= 1.1.0 - pydantic >= 2.0.0 ## Usage ### Starting the MCP Server The server runs using stdio transport (default for MCP): ```bash executor-mcp ``` Or run directly: ```bash python executor_mcp.py ``` ### Configuration Configure via environment variable: ```bash export EXECUTOR_LOG_DIR="$HOME/.executor-mcp/logs" executor-mcp ``` Default log directory: `.executor-mcp/` ### Configuring with Claude Desktop Add to your Claude Desktop configuration: **MacOS**: `~/Library/Application Support/Claude/claude_desktop_config.json` **Windows**: `%APPDATA%\Claude\claude_desktop_config.json` **Linux**: `~/.config/Claude/claude_desktop_config.json` ```json { "mcpServers": { "executor": { "command": "python", "args": ["/absolute/path/to/executor_mcp.py"], "env"…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.