SonarQube MCP
Related Servers
Alternatives to SonarQube MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to inspect SonarQube Cloud quality gates, analysis status, issues, security hotspots, measures, and per-line coverage, and to perform gated triage and review actions. It provides structured read tools plus optional restricted write tools for transitioning, assigning, commenting on, and bulk-updating findings.MIT
- AlicenseBqualityDmaintenanceRead-only MCP server that exposes SonarQube Web API tools for issue retrieval, quality gate status, and source context, enabling coding agents to fix code issues.8166 npm1MIT
- FlicenseNot gradedqualityBmaintenanceGives AI coding agents a shared local SonarQube instance plus a SonarQube MCP endpoint per machine, so multiple clients can run scans, wait on quality gates, and read metrics and issues for the auto-detected project in a workspace. Tools also accept an optional server argument to query configured remote SonarQube servers (such as a company CI server) alongside the local one.-

SonarQube MCP Serverofficial
FlicenseNot gradedqualityAmaintenanceEnables seamless integration with SonarQube Server or Cloud for code quality and security analysis. Supports querying project metrics, issues, and analyzing code snippets directly within the agent context.688-- FlicenseAqualityDmaintenanceA read-only MCP server that provides AI assistants with structured access to SonarQube projects, issues, metrics, and rules. It enables safe analysis of code quality and security findings through a set of validated, safety-first tools.6-
- FlicenseNot gradedqualityDmaintenanceEnables access to SonarQube code quality analysis through MCP, including issue searching, metrics retrieval, and quality gate status.-
TDQS
Scored across 6 tools
Most tools target clearly distinct resources: projects, branches, issues, issue source, measures, and quality gate. There is some potential overlap between sonarqube_quality_gate and sonarqube_measures because both surface ratings/metrics, and sonarqube_branches also includes quality gate status, but the descriptions make their scopes sufficiently distinct.
All tools use a consistent sonarqube_ prefix and snake_case resource-oriented naming. The convention is predictable throughout, with no mixed camelCase or inconsistent verb styles.
Six tools is well within the appropriate range and each tool maps to a core read-only SonarQube workflow. The surface is focused without obvious redundant tools.
The set covers project discovery, branches, unresolved issues, source context, measures, and quality gate explanation, forming a coherent triage workflow. Minor gaps exist for adjacent SonarQube data such as security hotspots and rule metadata, but core agent needs are covered.