Skip to main content
Glama
woffko

codex-mcp-longrun

by woffko

Related Servers

Alternatives to codex-mcp-longrun

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A 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.
      133
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Dependency-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.
      3
      320 PyPI
      46
      Business Source 1.1
    • A
      license
      Not graded
      quality
      C
      maintenance
      A minimal, zero-dependency MCP server that enables defining and running tools over stdio transport, without extra features like HTTP or resources.
      37 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides 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 npm
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency2/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues