Set up SonarQube MCP in Continue

Code quality analysis, security hotspot detection, and vulnerability tracking from SonarQube Cloud or Server. Official SonarSource implementation.

Locate the config file

Continue reads MCP server configuration from the following file:

~/.continue/config.yaml

Create this file if it does not already exist.

Add the configuration

Add the following to your Continue config file:

yaml

mcpServers:
  - name: sonarqube-mcp
    command: docker
    args:
      - run
      - --init
      - --pull=always
      - -i
      - --rm
      - mcp/sonarqube
    env:
      SONARQUBE_TOKEN: YOUR_SONARQUBE_TOKEN
      SONARQUBE_URL: YOUR_SONARQUBE_URL
      SONARQUBE_ORG: YOUR_SONARQUBE_ORG

Set up environment variables

SonarQube MCP requires the following environment variables:

SONARQUBE_TOKENRequired

SonarQube authentication token

SONARQUBE_URLOptional

SonarQube Server URL (omit for SonarQube Cloud)

SONARQUBE_ORGOptional

SonarQube Cloud organization key

Verify it works

Restart Continue. SonarQube MCP should appear in your MCP server list with 13 tools available.

This server adds approximately 6,500 tokens to your context window for tool definitions.

Set up SonarQube MCP in other editors

Claude Code Cursor VS Code Windsurf Claude Desktop

← Back to SonarQube MCP