MCP server tool support in Codex Web
Open 💬 4 comments Opened Sep 25, 2025 by jjangga0214
What feature would you like to see?
Hi!
It'd be great if Codex Cloud, not CLI, supports mcp.
As a workaround, could I copy my local ~/.codex/config.toml into the container’s setup script so that the configuration is automatically applied inside the container?
Are you interested in implementing this feature?
No, unfortunately, I do not know Rust well.
Additional information
Hope to use playwright mcp from cloud by the way.
(Haven't tested/found browser support from the container)
4 Comments
Did you ever figure a workaround out for this?
I’m trying to understand the point of using Codex Cloud without MCP support. I’ve spent a long time working on and refining AI SDLC workflows, and in my view, it’s practically impossible to build an effective AI-assisted development workflow without seamless integration with tools like Linear, Stitch, deployment tools, and others.
I think the only workaround is to use the REST APIs. In my experience, though, that approach isn’t ideal. Sometimes the agents seem to get lost or behave inconsistently when using them.
I wasted hours getting all of my skills local to my repo, setting up a container testing stack, getting scripts to install Serena, ollama, GrepAI. I create a config.toml in the fly, because my local one is used to patch codex app weirdness.
Everything works locally using the same base image. Setup and maintenance scripts work in the cloud environment.
But none of the MCP tools are discoverable in session, which makes all the above pointless.
Given cloud is also more expensive than local, and now with remote control, and this does not work, there is NO reason to use codex cloud EVER. Why adapt my repo with all the skills and AGENTS.md to work with a completely different workflow?
This is an important addition as "Tag" sessions run in the cloud environment and are blind to company context without MCP support.