-
Notifications
You must be signed in to change notification settings - Fork 7.3k
Open
Labels
ExtensionIssues related to the VS Code extensionIssues related to the VS Code extensionenhancementNew feature or requestNew feature or requestmcpIssues related to the use of model context protocol (MCP) serversIssues related to the use of model context protocol (MCP) servers
Description
What feature would you like to see?
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.jsonconfig 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.
Are you interested in implementing this feature?
No response
Additional information
No response
alleniver, MosheMuller173, Moishwbinet, bkniffler, iakov-ops and 50 more
Metadata
Metadata
Assignees
Labels
ExtensionIssues related to the VS Code extensionIssues related to the VS Code extensionenhancementNew feature or requestNew feature or requestmcpIssues related to the use of model context protocol (MCP) serversIssues related to the use of model context protocol (MCP) servers