Reported by @astral peak
Bug Report: Nested MCP servers not working
`Steps to Reproduce`
When I am working within a project directory, the nested MCP servers are recognised but fail to activate
Eg
- I open Codex App
- Navigate to a project repo, only my global MCP servers are available to use, the MCP servers nested in config.toml at the root level are not available
- The nested MCP servers are shown in the Codex App MCP Tab, so they are recognised but not activating
- When I go to the same project using the Codex CLI, the MCP servers are available to use
`Expected Result`
Nested MCP servers should be recognised and available to use, just like CLI
`Actual Result`
Nested MCP servers are found, but are unavailable to be called
`Environment`
Codex App MacOS