FIXED - [BUG] MCP server configuration is overridden by defaults when opening IDE

SonarQube for IDE Visual Studio
1

This affects all OSs from what my team states.

The issue here is that since today’s update of the vscode extension (6.0.0), the MCP configuration for the Connected Mode SonarQube Server is constantly replacing the config object.

If using mTLS to access the server, you may change the config for the MCP to look like:

  "sonarqube": {
    "command": "docker",
    "args": [
      "run",
      "--init",
      "--pull=always",
      "-i",
      "--rm",
      "--user",
      "0:0",
      "-e",
      "SONARQUBE_TOKEN",
      "-e",
      "SONARQUBE_URL",
      "-e",
      "SONARQUBE_IDE_PORT",
      "-v",
      "YOUR_FULL_PATH_TO_P12_FILE:/etc/ssl/mcp/user.p12:ro,z",
      "-e",
      "JAVA_OPTS",
      "sonarsource/sonarqube-mcp"
    ],
    "env": {
      "SONARQUBE_URL": "YOUR_SONARQUBE_URL",
      "SONARQUBE_TOKEN": "YOUR_SONARQUBE_USER_TOKEN",
      "SONARQUBE_IDE_PORT": "64121",
      "JAVA_OPTS": "-Djavax.net.ssl.keyStore=/etc/ssl/mcp/user.p12 -Djavax.net.ssl.keyStorePassword=YOUR_P12_FILE_PASSWORD -Djavax.net.ssl.keyStoreType=PKCS12"
    }
  }

This worked fine previously.

Since today’s updates, every time the IDE is opened, it gets replaced with:

  "sonarqube": {
    "command": "docker",
    "args": [
      "run",
      "--init",
      "--pull=always",
      "-i",
      "--rm",
      "-e",
      "SONARQUBE_TOKEN",
      "-e",
      "SONARQUBE_URL",
      "-e",
      "SONARQUBE_IDE_PORT",
      "sonarsource/sonarqube-mcp"
    ],
    "env": {
      "SONARQUBE_URL": "YOUR_SONARQUBE_URL",
      "SONARQUBE_TOKEN": "YOUR_SONARQUBE_USER_TOKEN",
      "SONARQUBE_IDE_PORT": "64120"
    }
  }

This is removing anything other than an bare minimal default.

This also breaks anyone who used the generator at: SonarQube MCP Server — mcp.sonarqube.com

This affects all users who customize the MCP setting for their server.

It is very unlikely this is intended behavior… If so, then I suggest a feature request to disable this.

4

Hi @SoN9ne, this is effectively an oversight on our side, and we did not intend to break such customizations. We are working on a fix and will provide a new bug fix release as soon as possible, ideally today. The update logic should only modify the IDE_PORT key and not the whole configuration.

6

We have just released a new fix version. Please let us know if you still notice any issue, or if you have any feedback. SonarQube for IDE should not be deleting any of your configuration anymore.

Once again, sorry for the inconvenience!

8

This works as expected now! Thank you so much for the fast turn-a-round!

These things happen, no worries. So glad to see such an immediate fix.