What feature would you like to see?

The mcp docs in the readme state:

The Codex CLI can be configured to leverage MCP servers by defining an mcp_servers section in ~/.codex/config.toml

So, there appears to be no way of setting up project specific MCP settings (e.g., using MCP server A in Project X via config in the Project X root location, while using MCP server B in Project Y).

Given the proliferation of MCP servers, and the difficulty of current models to handle large numbers of MCP tools, it is best to limit the MCP tools to only those required for the target project.

See Project Configuration in the Cursor docs for an example of project-specific MCP setups.

Are you interested in implementing this feature?

No

Additional information

No response