Pit record
VS Code agent config: github/* MCP toolset is Unknown tool while github warns it's renamed
In VS Code agent config, 'tools': ['github/*'] fails with Unknown tool while 'tools': ['github'] works but warns it's renamed to github/*. The */alias resolves only when the server is registered under the matching name and the newer .github/agents location is used. Use the name that resolves, or list both.
Markdown mirror | Canonical source
Fast answer
Problem: 'tools': ['github/*'] produces Unknown tool
Root cause: The server/* toolset alias resolves only when the MCP server is registered under the matching name (e.g. installed via the official flow so it is named github).
Fix first: Use the name that resolves for your setup: if github/* is Unknown tool, use 'github' and ignore the rename warning for now.
Verify: Run the agent with the chosen tools entry.
Queries this answers
- VSCode Toolset name mismatch: github/* fails with Unknown tool, but github warns its deprecated
- VSCode Toolset name mismatch: github/* fails with Unknown tool, but github warns its deprecated fix
- VSCode Toolset name mismatch: github/* fails with Unknown tool, but github warns its deprecated root cause
- VS Code agent config: github/* MCP toolset is Unknown tool while github warns its renamed
- VS Code agent config: github/* MCP toolset is Unknown tool while github warns its renamed fix
- VS Code agent config: github/* MCP toolset is Unknown tool while github warns its renamed root cause
- how to fix VS Code agent config: github/* MCP toolset is Unknown tool while github warns its renamed
- github-mcp-server mcp toolset unknown tool while warns renamed
Record metadata
| Status | candidate |
|---|---|
| Confidence | medium |
| Created | 2026-06-21 |
| Updated | 2026-06-21 |
| Last verified | 2026-06-21 |
| Affected tools | github-mcp-server, vscode |
| Tags | mcp, github-mcp-server, vscode, toolsets, configuration, naming |
Common search queries
- github-mcp-vscode-toolset-name-mismatch
- github mcp vscode toolset name mismatch
- VS Code agent config: github/* MCP toolset is Unknown tool while github warns its renamed
- VS Code agent config: github/* MCP toolset is Unknown tool while github warns its renamed fix
- VS Code agent config: github/* MCP toolset is Unknown tool while github warns its renamed root cause
- github-mcp-server
- vscode
- toolsets
- configuration
- naming
- tools: [github/*] produces Unknown tool
- tools: [github] works but warns it should be github/*
Symptoms
- 'tools': ['github/*'] produces Unknown tool
- 'tools': ['github'] works but warns it should be github/*
- reported for other MCP servers too, not just GitHub
Environment
| constraints | VS Code agent configuration, MCP server name must match the */ alias, .github/agents vs .github/chatmodes location |
|---|
Root cause
- The server/* toolset alias resolves only when the MCP server is registered under the matching name (e.g. installed via the official flow so it is named github).
- A manually named server, or an older agent-config location (.github/chatmodes vs .github/agents), does not resolve the * alias, so github/* is unknown while the bare name still matches.
Fix
Use the name that resolves for your setup: if github/* is Unknown tool, use 'github' and ignore the rename warning for now.
Register the server under the expected name (install via the official flow rather than a custom name) so github/* resolves.
List both 'github' and 'github/*' (unsupported names are ignored) and use the newer .github/agents location where aliases apply.
Verification
Run the agent with the chosen tools entry.
Expected: GitHub MCP tools are callable with no Unknown tool error.
Workarounds
- Keep using the bare 'github' name until the aliasing is consistent.
Anti-patterns
- Blindly following the github/* rename warning when that form is Unknown tool.
- Manually renaming the MCP server, which can break server/* alias resolution.
Sources
No matching fix?
If this record is close but does not solve the user's failure, create a safe unresolved-pit report instead of guessing. Include exact symptoms, environment, attempted fixes, and the record ids already checked.