You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support VSCode MCP Management and mcp.json Integration in Codex Extension #2901
I would like the Codex VSCode extension to support the same MCP (Model Communication Protocol) management system that is already used by GitHub Copilot in VSCode.
VSCode itself has built-in MCP management, using configuration files like mcp.json. GitHub Copilot leverages this and allows users to configure, select, and use multiple MCPs easily. Codex should do the same, so that:
The mcp.json config and VSCode's MCP management UI are recognized by Codex, just as they are by Copilot.
All MCPs configured for Copilot in VSCode should be available and manageable in Codex without needing to set them up again.
MCP/tool/plugin management is unified and interoperable between Copilot and Codex, since it's a VSCode feature and not just a Copilot one.
This would make setup and usage seamless for users of both Codex and Copilot, and encourage configuration reuse and best practices across both extensions.
We've recently improved the configuration mechanism for MCP servers inside of Codex. There's now a GUI-based settings panel. We've also recently added the ability to configure MCP servers on a per-project basis using project-local .codex/config.toml files.
All Codex local surfaces (the Codex CLI, VS Code extension, JetBrains extension, etc.) use the same configuration mechanism.
We don't plan to add support for Github copilot's configuration mechanism. That's a different tool chain, and it has its own configuration mechanism.
Reacted by Makarov Alexandr, Benyomin Mandel, jalapenopeppers and Igor Mytyuk
Activity
nicetomytyuk commentedon Sep 19, 2025
Were you able to make Codex on VS Code use the MCP?
Etsija commentedon Oct 29, 2025
No response in 2 months, so this is a no-go? Bummer, as this would be so good!
bhack commentedon Jan 8, 2026
This has reached 53 upvotes. Any news?
bhack commentedon Jan 10, 2026
E.g. see anomalyco/opencode#7122
etraut-openai commentedon Feb 1, 2026
We've recently improved the configuration mechanism for MCP servers inside of Codex. There's now a GUI-based settings panel. We've also recently added the ability to configure MCP servers on a per-project basis using project-local
.codex/config.tomlfiles.All Codex local surfaces (the Codex CLI, VS Code extension, JetBrains extension, etc.) use the same configuration mechanism.
We don't plan to add support for Github copilot's configuration mechanism. That's a different tool chain, and it has its own configuration mechanism.
Cretezy commentedon Mar 12, 2026
It seems like many tools support loading from
.mcp.json, is that planned?pdrosatlassian commentedon May 25, 2026
Not only copilot using mcp.json convention. Cursor, claude code, rovodev all support mcp.json format
biehlermi commentedon Jul 18, 2026
@etraut-openai Could you take another look at this suggestion? It would make sense to me to offer support for the mcp.json files as well.