Troubleshooting

What to do when you have problems engaging with the SonarQube MCP Server.

SonarQube MCP Server's logs will be written to the <STORAGE_PATH>/logs/mcp.log file, as defined by your Base variables.

If your MCP server is running in a container and you're using its default storage path, check the /app/storage/logs/mcp.log file within the running container.

When SONARQUBE_DEBUG_ENABLED is set to true, debug logging is enabled. Debug logs are written to both the log file and STDERR. This parameter is useful for troubleshooting connectivity or configuration issues. Default: false.

Common issues

"Feature is not working" or "Missing tools/functionality"

You may be running an outdated Docker image. Docker caches images locally, so you won't automatically receive updates.

Solution: Update to the latest version:

docker pull sonarsource/sonarqube-mcp:latest

After pulling the latest image, restart your MCP client to use the updated version.

Optionally, add the --pull=always flag to your docker run command to always check for and pull the latest version:

docker run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG sonarsource/sonarqube-mcp

"I want to pin to a specific version"

Browse available tags at sonarsource/sonarqube-mcp and reference the version you want:

docker pull sonarsource/sonarqube-mcp:1.21.0.2975

docker run --init -i --rm \
  -e SONARQUBE_TOKEN -e SONARQUBE_ORG \
  sonarsource/sonarqube-mcp:1.21.0.2975

In your MCP client config, use sonarsource/sonarqube-mcp:<version> instead of sonarsource/sonarqube-mcp and remove --pull=always so Docker doesn't silently upgrade the image.

For additional help, visit the Sonar Community forum.