Description

In cases where GitLens is unable to bundle the GitKraken MCP (GK MCP) (usually when an IDE does not support VS Code's bundled MCP API) a more manual setup process is required for the GK MCP to function. Since the bundled and manually setup GK MCP servers are different to an IDE, this can result in duplicate GK MCP servers being setup at once if an IDE starts supporting VS Code's bundled MCP API.

This issue is to explore cleaning up the manually setup versions of the GK MCP server when the bundled version also exists.

GK CLI version

UPD. 2025-11-21: CLI is fixed on core@3.1.48, installer@3.1.48.

Steps to reproduce

• Run VSCode

• Go to the folder where GK installer is installed

• Run ./gk mcp install vscode-insiders or ./gk mcp install vscode

  • If you launch VSCode from a custom profile folder then run ./gk mcp install vscode-insiders --source=gitlens. Then click "install" button on the "MCP Server: GitKraken" tab in VS Code.
  • If you launch in standard folder in debug sub-profile, make sure you use main mcp.json to list MCP servers:
    

• Install GitLens pre-release.

• Using VSCode palette run the command "MCP: List Servers"

Expected result

• previously installed (independent) GitKraken MCP is not in the list
• you see "GitKraken (bundled with GitLens)" MCP server only.

Actual result

you see both MCP servers:

• "GitKraken (bundled with GitLens)"
• "GitKraken" - global in VSCode