Same category · Developer tools
Snyk Studio MCP
Bring Snyk code, dependency, container, infrastructure, and related security scans into a local MCP workflow.
MCPby SonarSource · SonarSource/sonarqube-mcp-server
SonarSource provides an MCP server for SonarQube Cloud and Server. The official manual setup uses the sonarsource/sonarqube-mcp container image.
SonarSource provides an MCP server for SonarQube Cloud and Server. The official manual setup uses the sonarsource/sonarqube-mcp container image.
Illustrative saved transcript; historical tool calls and timings are not current API documentation or a live execution.
{
"mcpServers": {
"sonarqube": {
"command": "docker",
"args": [
"run",
"--init",
"--pull=always",
"-i",
"--rm",
"-e",
"SONARQUBE_TOKEN",
"-e",
"SONARQUBE_ORG",
"sonarsource/sonarqube-mcp"
],
"env": {
"SONARQUBE_TOKEN": "<YOUR_USER_TOKEN>",
"SONARQUBE_ORG": "<YOUR_ORG>"
}
}
}
}{
"mcpServers": {
"sonarqube": {
"command": "docker",
"args": [
"run",
"--init",
"--pull=always",
"-i",
"--rm",
"-e",
"SONARQUBE_TOKEN",
"-e",
"SONARQUBE_URL",
"sonarsource/sonarqube-mcp"
],
"env": {
"SONARQUBE_TOKEN": "<YOUR_USER_TOKEN>",
"SONARQUBE_URL": "<YOUR_SERVER_URL>"
}
}
}
}Use a user token and a running Docker daemon. For Cloud US, also pass SONARQUBE_URL=https://sonarqube.us in env and the Docker -e arguments. Keep tokens out of version control; replace placeholders locally.
Client/version scope: Claude Desktop / Cursor. Other clients: pending verification.
Suggested prompts, not measured outcomes. Installation and listed tools were reviewed; these workflows were not executed.
Use sonarqube-mcp. Top 5 rules by open-issue count in project 'foo'.
List every open issue for rule java:S2293 (Use Diamond Operator) — file, line, snippet.
For each, apply the rule's recommended fix. Keep changes minimal; don't reformat.
After my CI runs the next analysis, recheck the issue count for that rule.
Use sonarqube-mcp. Show quality gate status for PR 1234 — which conditions failed?
For 'New Coverage' below threshold — list new lines added in this PR with no test coverage.
Write tests covering those uncovered lines.
Use sonarqube-mcp. List all unreviewed security hotspots in project 'foo' grouped by category.
For each, summarize the risk in 1 line. Mark which are clearly safe-to-acknowledge vs need-fix.
For need-fix ones, apply the rule's safe pattern. For safe ones, give me the comment to leave on the hotspot review.
Integration compatibility: pending verification. Treat these as suggested workflows.
On every PR, comment Sonar's gate result and any new issues it added.
Fix all java:S2293 instances; write the diffs locally for review before commit.
Selected parameters checked against upstream definitions. Consult the connected server tools/list for your installed version.
projectKeys?: string[], branch?: string, pullRequest?: string, severities?: string[], issueStatuses?: string[], pageIndex?: integer, pageSize?: integer (1–500)Find project findings
projectKey?: string, projectId?: string, analysisId?: string, branch?: string, pullRequest?: stringInspect a project gate
api_quota: pending verification
per_call_tokens: pending verification
monetary: pending verification: see current upstream pricing and hosting requirements.
budget_tip: Limit requested data and inspect actual output before expanding queries.
SONARQUBE_TOKEN is a user token; Cloud also uses SONARQUBE_ORG, Server uses SONARQUBE_URL.
The configured SonarQube service; complete network audit pending review.
Pending verification: project permissions depend on selected tools
Use SONARQUBE_READ_ONLY=true when only reading findings.
CVE status and a full security audit: pending verification.
Check Docker, the official image, the user token, and the Cloud organization or Server URL.
Pending verification: alternative projects and tradeoffs have not been rechecked.
Documentation checked 2026-10-08. No authenticated service was executed. Unchecked claims are marked pending verification.