SonarQube MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SONARQUBE_URL | Yes | URL of your SonarQube instance, e.g. http://your-sonarqube-instance:9000 | |
| SONARQUBE_TOKEN | Yes | Your SonarQube authentication token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sonarqube_list_projectsB | List all accessible SonarQube projects with their basic information and quality status |
| sonarqube_get_project_metricsA | Retrieve comprehensive project quality metrics including coverage, technical debt, complexity, and issue counts |
| list_issuesB | List code quality issues from a SonarQube project with filtering options |
| get_security_vulnerabilitiesC | Get detailed security vulnerability analysis from a SonarQube project |
| get_quality_gateB | Get quality gate status and conditions for a SonarQube project |
| get_analysis_historyB | Get historical analysis data and trends for a SonarQube project |
| get_project_repositoryB | Get git repository information and source code management details for a SonarQube project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct SonarQube resource: project listing, metrics, quality gate, issues, security vulnerabilities, analysis history, and repository info. No overlap in purpose.
Most tools use verb_noun snake_case (e.g., get_analysis_history), but two tools include a 'sonarqube_' prefix (sonarqube_get_project_metrics, sonarqube_list_projects), breaking the pattern. The convention is mixed but still readable.
7 tools is well-scoped for a SonarQube analysis server, covering the primary read operations without redundancy.
Covers major reading operations (metrics, issues, security, quality gate), but misses some likely endpoints like 'get_project' for a single project or 'get_issue' for a specific issue. Minor gaps that agents can work around.