Skip to content

fix: align Implementation.Name with VS Code config key#2577

Open
SamMorrowDrums wants to merge 1 commit into
mainfrom
fix/vscode-toolset-name-mismatch
Open

fix: align Implementation.Name with VS Code config key#2577
SamMorrowDrums wants to merge 1 commit into
mainfrom
fix/vscode-toolset-name-mismatch

Conversation

@SamMorrowDrums
Copy link
Copy Markdown
Collaborator

Sets the protocol-level Implementation.Name to "github" so the slug matches the configuration key VS Code derives from server.json's title. Without this, references using the recommended github/* tool prefix surface as Unknown tool 'github/github-mcp-server/*'.

The MCP registry name in server.json (io.github.github/github-mcp-server) intentionally still uses the source-repo's last segment per the registry naming convention — only the client-facing Implementation.Name changes here. A comment on NewServer documents the divergence so future contributors don't try to "re-sync" them.

Replaces #2043 (force-pushed branch, original commit lost). Co-authored to @yashhzd.

Fixes #1402

Verification

  • script/lint — clean
  • go test ./pkg/github -run TestNewServer_NameAndTitleViaTranslation -count=1 — passes (test expectations updated)
  • script/test — passes

Set the protocol-level Implementation.Name to "github" so the slug
matches the configuration key VS Code derives from server.json's title.
This fixes "Unknown tool 'github/github-mcp-server/*'" when references
use the recommended "github/*" pattern.

The MCP registry name in server.json
(io.github.github/github-mcp-server) intentionally still uses the
source-repo's last segment per the registry naming convention; only the
client-facing Implementation.Name changes here.

Fixes #1402

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@SamMorrowDrums SamMorrowDrums requested a review from a team as a code owner May 30, 2026 09:20
Copilot AI review requested due to automatic review settings May 30, 2026 09:20
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Aligns the MCP Implementation.Name default with the configuration key VS Code derives from server.json's title ("github"), so tool prefixes like github/* resolve instead of producing Unknown tool 'github/github-mcp-server/*'. The registry identifier in server.json intentionally remains distinct, per the MCP registry naming convention; a doc comment on NewServer records this divergence.

Changes:

  • Change default SERVER_NAME translation default from "github-mcp-server" to "github" in NewMCPServer.
  • Update the empty-string fallback in NewServer and its doc comment to match, including a note explaining the divergence from the registry name.
  • Update TestNewServer_NameAndTitleViaTranslation defaults expectation accordingly.
Show a summary per file
File Description
pkg/github/server.go Changes default server name to "github" and updates NewServer doc comment
pkg/github/server_test.go Updates test default-name expectation and translator default

Note: README.md (around line 1569) still documents the SERVER_NAME default as github-mcp-server and should be updated to reflect the new default, but that file is not part of this diff.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 0

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

3 participants