Does not add MCP to allowlist

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

As mentioned multiple times in other bug reports using mcp tool gitlens-extension-GitKraken keeps prompting to add to allowlist or run. When clicking “Allowlist MCP Tool” button it doesn’t add it to the allowlist.

Steps to Reproduce

  • Install gitlens extension
  • Setup gitlens mcp tool (or done automatically)
  • Prompt cursor to use git features like commit using the tool if it doesn’t automatically choose to do so

Expected Behavior

It should add this tool to allowlist

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.4.27 (system setup)
VSCode Version: 1.105.1
Commit: 4f2b772756b8f609e1354b3063de282ccbe7a690
Date: 2026-01-31T21:24:58.143Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.19045

Additional Information

I can actually see this tool in the allowlist, however it still prompts as if its not there.
(Don’t know how to view full names)

Other reports with same issue:

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This is a known issue with the MCP allowlist. The root cause is that the server IDs didn’t match between what gets saved in the allowlist and what gets checked when a tool is called.

Key point: you’re on version 2.4.27 from January 31, and the main fixes for this bug shipped on February 7 to 10. Please update to the latest version via Help > Check for Updates.

If the issue still happens after updating, reply here and we’ll dig in. The team knows extension-provided MCP servers, like GitLens, are especially tricky because their IDs have a more complex format.

Hi there, thanks for swift reply. I updated the ide as you mentioned and now it works like a charm. I keep getting update popup every time i turn cursor ide on, i click update so i thought it does it, but perhaps something fails with that flow.

Anyway, original issue fixed at least on my end with:

Version: 2.6.19 (system setup)
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045