SonarQube MCP server broken in latest VSCode

SonarQube MCP Server
1

We have been using the SonarQube MCP server, however it is no longer working with the latest version of VSCode (1.107+) as it not longer starts.

It looks like this VSCode version is supporting the latest MCP spec and the SonarQube MCP server is not understanding it, as it does not know what the new form field is.

[error] Error: MPC -32603: Unrecognized field "form" (class io.modelcontextprotocol.spec.McpSchema$ClientCapabilities$Elicitation), not marked as ignorable (0 known properties: ])
 at [Source: UNKNOWN; byte offset: #UNKNOWN] (through reference chain: io.modelcontextprotocol.spec.McpSchema$InitializeRequest["capabilities"]->io.modelcontextprotocol.spec.McpSchema$ClientCapabilities["elicitation"]->io.modelcontextprotocol.spec.McpSchema$ClientCapabilities$Elicitation["form"])
    at R8i.O (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2265:35574)
    at R8i.L (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2265:35369)
    at Sce.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2265:34358)
    at E.C (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29:2349)
    at E.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29:2568)
    at cMs.pushMessage (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:604:55563)
    at lli.$onDidReceiveMessage (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:604:52099)
    at zRt.S (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3894:40815)
    at zRt.Q (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3894:40593)
    at zRt.M (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3894:39681)

Please could the MCP server be update to support the latest MCP specs.

1 Like
Sonar Community Roundup; Dec 12, 2025 - Jan 9, 2026
4

Hey @robertsa1-els, thanks for reporting this problem. I’ve fixed the issue and it should be part of the next version. Long story short - we should not fail while parsing unknown properties.

I’ll also update to the latest version of the spec.

1 Like
5

Thanks for much for the speedy response and fix.

Look forward to it being released :slight_smile:

1 Like
8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

9

Hi @robertsa1-els,

Just to close the loop, the latest release is now live :slight_smile: Please let us know in case the issue persists.

All the best,
Sophio

1 Like