VSCode: Toolset name mismatch: 'github/*' fails with Unknown tool, but 'github' warns it's deprecated

[LorcanChinnock]

Describe the bug

When referencing the GitHub MCP toolset inside a VS Code agent configuration, using the recommended github/* pattern does not work.

• Referencing the toolset as github/* results in an Unknown tool error.

• Referencing the toolset simply as github works, but produces a warning stating that it has been renamed to github/*.

This creates a contradictory situation where:

• The recommended name (github/*) fails.
• The fallback name (github) works but warns that it should be replaced with github/*.

Affected version

I am using the remote GitHub MCP integration inside VS Code, so it does not expose a version.

VS Code version:
1.106.0

OS:
macOS Sequoia Version 15.7.2 (24G325)

Steps to reproduce the behavior

1. In a VS Code agent configuration, reference the GitHub MCP toolset like this:

   "tools": ["github/*"]

2. VS Code reports an error:

   Unknown tool 'github/github-mcp-server/*'.
   

3. Change the reference to:

   "tools": ["github"]

4. The agent loads, but VS Code shows a warning:

   Tool or toolset 'github' has been renamed, use 'github/*' instead.
   

Expected vs actual behavior

Expected behavior:
Referencing the toolset as github/* should work without errors and should be the correct, supported naming format.

Actual behavior:

• github/* → Fails with Unknown tool
• github → Works, but warns that the toolset has been renamed to github/*, which cannot actually be used

Logs

Unknown tool error:

Unknown tool 'github/github-mcp-server/*'.

Renaming warning:

Tool or toolset 'github' has been renamed, use 'github/*' instead.

[GordonBeeming]

I'm getting the same thing for close to 2 weeks now... thought it was a iss-me but looks to be an issue 😕

This affects all MCPs it looks like, not just the github tools

[Chuxel]

cc @aeschli on the VS Code team to look. How where the MCP servers installed here? @aeschli mentioned that if you install via @mcp it should have the right name, but if you manually name the MCP server something else, this could happen.

One note is that tactically you can list both tools and the respective products will ignore anything not supported. I also do not think these aliases will work in the old .github/chatmodes location, only .github/agents.

[yurideon]

Thanks for looking into it!

Having the same problem. Just to add some context, I installed github MCP by pressing the "button" on the README page, which adds

	"github": {
		"type": "http",
		"url": "https://api.githubcopilot.com/mcp/"
	}

to the mcp.json file.

And in the same way, "tools": ["github/*"] doesn't work, while "tools": ["github"] allows the agent mode to access github MCP.
I'm using it with a custom "agent" in .github/agents folder.

[aeschli]

@connor4312 @sandy081
We need to encourage user to install MCP servers via the MCP marketplace. The 'Install Server' button should redirect to do that.

[JeelRajodiya]

For some context, I'm having the same issue with playwright mcp server as well.

My mcp.json file:

When I create a custom agent, I get these error and I can't use both playwright or github mcp with custom agent.
But if I use the default agent which comes with copilot, it works without any issues.

Note that, I don't face any issues while using context7 mcp server