Skip to content

Update MCP documentation to use mcp.json file instead of settings.json in VS Code #46327

Open

Description

@ashis-baral

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/copilot/how-tos/copilot-in-your-ide/customize-copilot/extend-copilot-with-tools-and-context/extend-copilot-chat-with-mcp#configuring-mcp-servers-manually

What part(s) of the article would you like to see updated?

The article states:


Your personal instance of Visual Studio Code. You will be the only person who has access to configured MCP servers. To do this, add the configuration to your settings.json file in Visual Studio Code. MCP servers configured this way will be available in all workspaces.

However, this instruction does not work as expected with Visual Studio Code.

When I add the MCP server configuration to settings.json, the MCP server does not work. When I add the same configuration to mcp.json, the MCP server works correctly.

Additionally, when I open the Command Palette and run MCP: Open User Configuration, Visual Studio Code opens mcp.json, not settings.json.

Additional information

The documentation should specify the correct configuration file and provide accurate instructions for configuring user-level MCP servers that are available across workspaces.

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Oct 15, 2026
  2. added
    triageDo not begin working on this issue until triaged by the team
    on Oct 15, 2026
  3. changed the title [-]Update MCP documentation to use `mcp.json` instead of `settings.json` in VS Code[/-] [+]Update MCP documentation to use `mcp.json` file instead of `settings.json` in VS Code[/+] on Oct 15, 2026
  4. removed
    triageDo not begin working on this issue until triaged by the team
    on Oct 15, 2026
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

    contentThis issue or pull request belongs to the Docs Content team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions