Skip to content

Support VSCode MCP Management and mcp.json Integration in Codex Extension #2901

Closed as not planned

Description

@BenyominMandel

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.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.

Are you interested in implementing this feature?

No response

Additional information

No response

Activity

  1. nicetomytyuk commented on Sep 19, 2025

    @nicetomytyuk

    Were you able to make Codex on VS Code use the MCP?

  2. Etsija commented on Oct 29, 2025

    @Etsija

    No response in 2 months, so this is a no-go? Bummer, as this would be so good!

  3. added
    mcpIssues related to the use of model context protocol (MCP) servers
    on Oct 29, 2025
  4. bhack commented on Jan 8, 2026

    @bhack

    This has reached 53 upvotes. Any news?

  5. bhack commented on Jan 10, 2026

    @bhack
  6. etraut-openai commented on Feb 1, 2026

    @etraut-openai
    Contributor

    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.

  7. Cretezy commented on Mar 12, 2026

    @Cretezy

    It seems like many tools support loading from .mcp.json, is that planned?

  8. pdrosatlassian commented on May 25, 2026

    @pdrosatlassian

    Not only copilot using mcp.json convention. Cursor, claude code, rovodev all support mcp.json format

  9. biehlermi commented on Jul 18, 2026

    @biehlermi

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestextensionIssues related to the VS Code extensionmcpIssues related to the use of model context protocol (MCP) servers

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions