SonarSource · Gemini CLI
Add the SonarQube MCP server to Gemini CLI
Check code quality and security issues with SonarQube Server or Cloud.
Official serverLocalSecurity & code quality
1. Add the server
Run in your terminal
gemini mcp add -e SONARQUBE_TOKEN=YOUR_VALUE sonarqube docker run -i --rm -e SONARQUBE_TOKEN docker.io/sonarsource/sonarqube-mcp
2. Sign in
Run /mcp auth <name> inside Gemini CLI to sign in to an OAuth server. SonarQube runs locally and needs SONARQUBE_TOKEN. Replace the placeholder values above with your own before starting Gemini CLI.
3. Try it
Ask Gemini CLI for something SonarQube can do. Check code quality and security issues with SonarQube Server or Cloud. Approve the first tool call and check the result before allowing write actions automatically.
- · In settings.json, streamable HTTP servers use httpUrl, SSE servers use url, local servers use command.
- · includeTools and excludeTools limit which tools the model sees.
FAQ
- How do I add the SonarQube MCP server to Gemini CLI?
- Run: gemini mcp add -e SONARQUBE_TOKEN=YOUR_VALUE sonarqube docker run -i --rm -e SONARQUBE_TOKEN docker.io/sonarsource/sonarqube-mcp. Run /mcp auth <name> inside Gemini CLI to sign in to an OAuth server.
- Is this the official SonarQube MCP server?
- Yes. It is published by SonarSource as io.github.SonarSource/sonarqube-mcp-server in the official MCP registry.
- Does the SonarQube MCP server need an API key?
- Yes. It runs locally and requires SONARQUBE_TOKEN.
Links
SonarQube in other clients
More security & code quality for Gemini CLI
Work at SonarSource?
Feature SonarQube across the directory and its category from $49/month.
Reviewed Oct 5, 2026. Command generated from the registry record and checked against Gemini CLI's documented syntax.