codex-mcp-longrun
Related Servers
Alternatives to codex-mcp-longrun
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA local STDIO MCP server that bridges MCP clients to the Codex CLI by sending instructions to a configured workspace, exposing task run, status, and result tools with a read-only sandbox and no remote transport.133MIT
- AlicenseAqualityAmaintenanceDependency-free, locally sandboxed MCP stdio server. Tools run as WASM inside a capability-based WASI sandbox (wasmtime); every tools/call is attested with cost/policy and signed manifests fail-closed.3320 PyPI46Business Source 1.1
- AlicenseNot gradedqualityCmaintenanceA minimal, zero-dependency MCP server that enables defining and running tools over stdio transport, without extra features like HTTP or resources.37 npm1MIT
- FlicenseBqualityCmaintenanceA minimal MCP server that exposes a run_command tool over stdio, enabling command execution within a Docker container.1-
- AlicenseNot gradedqualityBmaintenanceA command execution MCP server supporting local execution, sandbox isolation via Docker/OpenSandbox, and SSH remote execution.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a deterministic set of 40 cross-platform command tools as an MCP server, replacing unsafe raw shell calls with structured JSON inputs and outputs for file system, process, network, and git operations.9 npmApache 2.0
TDQS
Scored across 3 tools
Each tool has a distinct role: health checks server status, run_and_wait executes a process and returns a result, and read_log_tail retrieves logs for a specific job. There is no overlap or ambiguity between them.
Tool names are inconsistent in style: 'health' is a simple noun, 'run_and_wait' is a verb phrase, and 'read_log_tail' is a verb-noun-noun compound. No uniform pattern (e.g., verb_noun) is followed.
Three tools is a minimal set, but it covers the core needs of a long-run execution server: health check, run a command, and read logs. It feels slightly thin but is not unreasonably sparse for a focused utility.
The surface covers the basic workflow of running a process and checking its logs, but lacks obvious lifecycle management tools like cancel, list jobs, or check status. The domain is narrow, yet significant gaps remain for robust long-running job handling.