`config.toml` missing/not recognized

Resolved 💬 2 comments Opened Aug 6, 2025 by Shaurya-Sethi Closed Aug 7, 2025
💡 Likely answer: A maintainer (bolinfest, collaborator) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.14.0

Which model were you using?

codex-mini

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What steps can reproduce the bug?

On installing codex cli, and following the instructions on the github README for adding MCP servers, I inspected the .codex folder at user home and noticed that the mentioned config.toml file does not exist - instead, a config.json exists.

Regardless, I made a config.toml with the exact mcp configuration mentioned and then started codex but it was unable to discover and use the mcp server (I use context7 a lot).

Additionally, any updates to config.json were also redundant and unrecognized by codex.

What is the expected behavior?

Expected codex to recognize the mcp server and be able to use its tools after configuring it as mentioned in the documentation.

What do you see instead?

No relevant logs can be found to further investigate the issue

Additional information

The same MCP server works with copilot, cline and gemini-cli. I can assure that its not a problem with the server.

View original on GitHub ↗

2 Comments

bolinfest collaborator · 1 year ago

config.json is legacy from the old TypeScript implementation of the CLI

Are you trying to use this on Windows or with WSL? We only really support WSL.

Shaurya-Sethi · 1 year ago

I was using it with windows, I'll try it out with WSL. Thanks!