feat: exec-command-mcp

[bolinfest]

To test:

cd codex-rs/exec-command-mcp
cargo build
npx @modelcontextprotocol/inspector ../target/debug/exec-command-mcp

Then in the inspector, expand the Configuration on the left and make the timeouts absurdly large.

Then hit Connect and List Tools like normal and choose the functions.exec_command tool.

Then for the cmd, use:

count=0
while true; do
  echo "$count"
  ((count++))
  sleep 1
done

and maybe reduce yield_time_ms to something relatively short, like 4000:

You should see only three numbers print (because the timeout is 4000) and make note of the sessionId, which is likely 0 if this is your first tool call:

Now change to the functions.write_stdin tool and change yield_time_ms to something like 5000, but most importantly, change session_id to match whatever you got back from the previous request:

Now the response let the tool run for yield_time_ms and include new output from that timeperiod, though if there is room in max_output_tokens, it will include more of the backlog:

I'm also trying the following in my config.toml after doing cargo build in /Users/mbolin/code/codex4/codex-rs:

experimental_disable_built_in_shell_tool = true

[mcp_servers.server-name]
command = "/Users/mbolin/code/codex4/codex-rs/target/debug/exec-command-mcp"

[bolinfest]

Closing this in favor of #2574.