Documentation update for connection to OpenAI Codex

[cpjet64]

Here are working examples of different MCP Client connection configs for OpenAI Codex:

Windows 11 Docker Desktop (Codex running in CMD or Powershell)

[mcp_servers.docker-mcp-gateway]
args = ["mcp", "gateway", "run"]
command = "docker.exe"

Windows 11 Docker Desktop (Codex running in WSL Distro such as Ubuntu)

[mcp_servers.docker-gateway]
command = "/mnt/c/Program Files/Docker/Docker/resources/bin/docker.exe"
args = ["mcp", "gateway", "run"]

[slimslenderslacks]

@cpjet64 thank you for this.

Perhaps we can also use this to track an update to the docker mcp client connect codex command to make this update. At the moment, I think we're just looking for a round-tripping toml parser.

[cpjet64]

@cpjet64 thank you for this.

Perhaps we can also use this to track an update to the docker mcp client connect codex command to make this update. At the moment, I think we're just looking for a round-tripping toml parser.

So I should add that while these are the correct configs to use for Codex, the codex team still has not fixed the environment issues in windows just yet so I figured out a WORKAROUND to get it to work. As for making a roundtrip toml parser I would be more than happy to invest some time in making one if it will actually get used. Any code requirements for it? I mainly work in Rust, Python, & C# and other languages I just use agentic coding tools with lots of testing.

[slimslenderslacks]

Thanks, that would be amazing. For the json edits, we've been using github.com/mikefarah/yq/v4 v4.45.4 to make edits, but I think that has limited support for editing toml files. Ideally, we can:

1. list each mcp_server and check for ones with a particular name (eg {our_name})
2. add missing mcp_server entries
3. delete the mcp_server.{our_name} entry if the user disconnects

And make sure that we preserve all comments and formatting for any edits that we make.

To be honest, if you just ask codex to edit it's own file, it does a fine job, so it feels kind of odd that we're trying to find a good toml parser :)

[cpjet64]

So after about 10 hours of digging into this deeply I discovered that codex has new commands and flags etc...

Long story short theres no need for a parser at all because now Codex can modify its mcp server configs itself.

If you want to plumb these in or I can fork and do it for you and then PR? Just let me know!

Here are the commands:

Add MCP Server

• Windows 11 Docker Desktop (Codex running in CMD or Powershell) (w/o env vars)

codex mcp add docker-mcp-gateway -- docker.exe mcp gateway run

• Windows 11 Docker Desktop (Codex running in CMD or Powershell) (w/ env vars)

codex mcp add docker-mcp-gateway `
  --env APPDATA="C:\Users\$env:USERNAME\AppData\Roaming" `
  --env COMSPEC="C:\Windows\System32\cmd.exe" `
  --env HOMEDRIVE="C:" `
  --env HOMEPATH="\Users\$env:USERNAME" `
  --env LOCALAPPDATA="C:\Users\$env:USERNAME\AppData\Local" `
  --env POWERSHELL="C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" `
  --env PROGRAMDATA="C:\ProgramData" `
  --env PROGRAMFILES="C:\Program Files" `
  --env PWSH="C:\Program Files\PowerShell\7\pwsh.exe" `
  --env SYSTEMDRIVE="C:" `
  --env SYSTEMROOT="C:\Windows" `
  --env TEMP="C:\Users\$env:USERNAME\AppData\Local\Temp" `
  --env TMP="C:\Users\$env:USERNAME\AppData\Local\Temp" `
  --env USERPROFILE="C:\Users\$env:USERNAME" `
  -- docker.exe mcp gateway run

• Windows 11 Docker Desktop (Codex running in WSL Distro such as Ubuntu)

codex mcp add docker-mcp-gateway -- "/mnt/c/Program Files/Docker/Docker/resources/bin/docker.exe" mcp gateway run

Remove MCP Server

codex mcp remove docker-mcp-gateway

[slimslenderslacks]

Oh wow, great find @cpjet64.

I've started a PR #165 to integrate this. So we'll use the existence of the command on the current shell to determine whether or not it's installed and then I've built up from there.

[cpjet64]

Glad to of been of service!

[slimslenderslacks]

It almost seems impossible to use codex from WSL given how much enviroment you have to copy in.

[xenoscopic]

It almost seems impossible to use codex from WSL given how much enviroment you have to copy in.

Some people already more or less live in WSL - ~/.ssh, dotfiles, tools, etc., so it's not too far fetched that they might have their environment ready to go. (Windows is just a hypervisor for them).