sonarqube-mcp-py
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for HTTP transport (default: 8959) | 8959 |
| MCP_TRANSPORT | No | Transport mode: 'stdio' (default) or 'streamable-http' | stdio |
| SONARQUBE_URL | Yes | The URL of your SonarQube instance (e.g., https://your-sonarqube-instance) | |
| SONARQUBE_TOKEN | Yes | Your SonarQube authentication token (e.g., squ_your_token_here) | |
| SONARQUBE_VERIFY_SSL | No | Set to 'false' to disable SSL verification for self-signed certificates (default: 'true') | true |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_sonarqube_projectsC | Search for projects in SonarQube |
| get_project_quality_gate_statusC | Get quality gate status for a project |
| get_component_measuresC | Get metrics for a component (bugs, coverage, etc.) |
| list_quality_gatesA | List all quality gates defined in SonarQube |
| search_sonar_issuesC | Search for issues (bugs, vulnerabilities, code smells) in a project |
| search_security_hotspotsC | Search for security hotspots in a project |
| show_security_hotspotC | Get details of a specific security hotspot |
| show_ruleC | Get details of a SonarQube rule |
| search_metricsA | List all available metrics in SonarQube |
| list_pull_requestsC | List pull requests analyzed for a project |
| get_file_coverage_detailsC | Get coverage details for files in a project |
| search_files_by_coverageD | Find files with lowest coverage |
| get_duplicationsC | Get code duplications for a file |
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 13 tools
Each tool targets a distinct aspect of SonarQube (measures, duplications, coverage, quality gates, pull requests, metrics, hotspots, issues, projects, rules). Even similar tools like 'get_file_coverage_details' and 'search_files_by_coverage' have clearly different purposes.
Tools follow a verb_noun pattern (get_, list_, search_, show_) but verbs are mixed inconsistently: 'list' for pull requests and quality gates, 'search' for issues and projects, 'get' for measures and duplications, 'show' for rules and hotspots. While the meaning is clear, unified verb choice would improve consistency.
13 tools is well-scoped for a SonarQube server, covering core inspection and analysis functionalities without being overwhelming. Each tool earns its place.
The set covers key read/query operations (measures, duplications, coverage, quality gates, pull requests, issues, hotspots, projects, rules). Minor gaps exist: no dedicated 'get_issue' or 'get_project' tool for individual details, but search tools provide workarounds.