SonarQube

Official Sonar Security

Lets an agent check code quality and security using SonarQube Server or Cloud. Summary written by AI Index.

The registry’s description: Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.

Local package (oci) Needs a key: SONARQUBE_TOKEN

Add to your client

Add the SonarQube MCP server to Claude Code

  1. Run the command

    claude mcp add -e SONARQUBE_TOKEN=<SONARQUBE_TOKEN> sonarqube -- docker run -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG -e SONARQUBE_URL docker.io/sonarsource/sonarqube-mcp
  2. Fill in the values ↓

  3. Check it’s connected

If the file already has servers, add the entry inside the existing object. To check it’s connected, restart or reload the client and look for sonarqube in its list of MCP servers. A server that needs sign-in opens it on first use.

What you fill in

Required values appear as <NAME> placeholders in the snippets; add optional ones the same way. Descriptions are the server’s registry entry’s.

  • <SONARQUBE_TOKEN> Environment variable Required · Secret

    Your SonarQube USER token

  • <SONARQUBE_ORG> Environment variable Optional · Secret

    Your SonarQube Cloud organization key (if using SonarQube Cloud)

  • <SONARQUBE_URL> Environment variable Optional · Secret

    Your SonarQube Server URL (if using SonarQube Server)

Client compatibility

By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.

Sources

This data comes from the Official MCP Registry.