Add the SonarQube MCP server to Claude Code
Config last verified Jun 1, 2026
The exact config to run SonarQube in Claude Code — paste it in, restart, and the tools load.
Prerequisites
- Claude Code installed.
- SONARQUBE_TOKEN — SonarQube Cloud or Server token used to authenticate API calls.
Setup
1. Open ~/.claude.json
2. Add this configuration
Add to ~/.claude.json
~/.claude.json
json
{
"mcpServers": {
"sonarqube": {
"command": "docker",
"args": [
"run",
"--init",
"--pull=always",
"-i",
"--rm",
"-e",
"SONARQUBE_TOKEN",
"-e",
"SONARQUBE_ORG",
"mcp/sonarqube"
],
"env": {
"SONARQUBE_TOKEN": "<SONARQUBE_TOKEN>",
"SONARQUBE_ORG": "<SONARQUBE_ORG>"
}
}
}
}Or via CLI
bash
claude mcp add sonarqube -- docker run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG mcp/sonarqube3. Restart Claude Code and confirm the SonarQube tools load.
Gotchas
Claude Code stores MCP servers under an "mcpServers" object in ~/.claude.json. It also reads a project-scoped .mcp.json and supports adding servers from the command line with "claude mcp add". Each entry must declare either a "type" or a "command"; Claude Code refuses an entry that has neither. Remote servers connect natively over Streamable HTTP with OAuth.