github / github/github-mcp-server

VSCode MCP Registry integration does not support latest MCP registry

Offen
#1,459 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
Go
Sterne
33k
Forks
5k
Ø Merge
2 T. 1 Std.
Gemergte PRs (30 T.)
52

Beschreibung

### Describe the bug
When attempting to connect to VSCode to setup the MCP Registry integration, it is expecting the schema for the json to be "2025-9-29".
When attempting to setup the integration with the open source MCP registry from the mcp group, which uses schema "2025-10-17", we are seeing serialization errors in VSCode.

### Affected version
VSCode 1.106.1 and 1.107

### Steps to reproduce the behavior

1. Setup MCP Registry that uses "2025-10-17" Schema.
2. In the GitHub Copilot admin console for my enterprise, add the url to the MCP Registy.
3. Open VSCode and sign into my GitHub account.
4. Search for MCP servers in the extension view.
5. See serialization error in the Output view -> Window, MCPs do not populate in extensions view.

### Expected vs actual behavior
Expected: MCP servers populate extensions view when searched.
Actual: Extensions view is blank and serialization error is seen in Output view -> Window

### Logs
2025-11-20 09:15:41.801 [error] [Window] Failed to serialize MCP servers result from https://solo-mcp-registry-route.com/v0.1/servers: Error: Failed to serialize MCP servers result from https://solo-mcp-registry-route..com/v0.1/servers
at KZe.n (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1362:16787)
at async KZe.m (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1362:16176)
at async KZe.query (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1362:13303)
at async fgt.queryGallery (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:2566:10201)
at async C_.kc (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:2566:957)
at async C_.show (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:2564:9718)
at async vscode-file://vscode-app/c:/Users//AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:2489:44227
at async Promise.all (index 0)
at async r (vscode-file://vscode-app/c:/Users//AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1297:13142)

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.