SonarQube Cloud over MCP: quality gates, issues, hotspots, measures, coverage and issue triage.
Maintain this server? Claim it
This server only runs locally, from a package. Install it with the instructions on this page to try it.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add sonarqube-mcp \ -e SONARQUBE_TOKEN=YOUR_SONARQUBE_TOKEN \ -- dnx [email protected] --yes
Environment
SONARQUBE_TOKEN (required): SonarQube Cloud user token, sent as a Bearer credential. Create one at https://sonarcloud.io/account/security and pick the User Token type - a project analysis token is not accepted by these endpoints. Without it the server still starts and reads public projects anonymously, but nothing private is reachable and no write tool works.SONARQUBE_ORG (optional, not in the config above): Organization key - the last segment of https://sonarcloud.io/organizations/{key}. Only listProjects and getRule require it, and a public organization answers both anonymously, so it is optional; set it and every project in that organization becomes discoverable.SONARQUBE_URL (optional, not in the config above): Base URL of the SonarQube Cloud instance. Defaults to https://sonarcloud.io; the only other accepted host is https://sonarqube.us. SonarQube Server is out of scope and any other value is ignored.SONARQUBE_MCP_DEFAULT_PROJECT (optional, not in the config above): Project key used when a tool call omits projectKey. It is the id in a sonarcloud.io project URL, not the repository name. Setting it is worth it when this server is configured per checkout.SONARQUBE_MCP_READ_ONLY (optional, not in the config above): Set to 1 to register only the eighteen read tools. The five write tools - transitionIssue, assignIssue, addIssueComment, setHotspotStatus and bulkUpdateIssues - are then absent from tools/list rather than refused when called.We don't run packages, so we can't list this server's tools.