SonarQube MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SONARQUBE_URL | No | SonarQube base URL | https://sonarqube-engops-production.opengov.teleport.sh |
| SONARQUBE_TOKEN | Yes | SonarQube user token (squ_...) | |
| SONARQUBE_PROJECT | No | SonarQube project key | payroll-app-web |
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 |
|---|---|
| sonar_get_pr_issuesA | Get all open SonarQube issues for a specific pull request, grouped by file. Use this when the user asks about issues on their PR, branch, or 'what does Sonar say'. Returns each file with its issues (rule, line, severity, message). |
| sonar_get_file_issuesA | Get open SonarQube issues for a specific source file. Use this when the user asks about issues in a particular file they are editing or viewing. Returns the list of issues with line number, rule, severity, and fix message. |
| sonar_get_pr_metricsA | Get quality metrics for a pull request: coverage on new code, duplication percentage, and issue counts (bugs, code smells, vulnerabilities). Use this when the user asks 'what is my coverage?', 'does Sonar pass?', or 'what are the Sonar metrics on my PR?'. |
| sonar_get_duplication_reportA | Get the duplicated lines report for a pull request — which files have duplicated code and what percentage. Use this when the user mentions 'duplication' or 'duplicated lines'. |
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 4 tools
Each tool targets a distinct aspect of SonarQube data: duplication, file issues, PR issues, and PR metrics. No overlap in functionality.
All tools follow a consistent 'sonar_get_<descriptive_noun_phrase>' pattern, using snake_case throughout.
4 tools cover the essential read operations for SonarQube integration, neither too few nor too many for the domain.
Covers key retrieval needs (duplication, file-level issues, PR issues, metrics). Missing quality gate status check, but core workflows are addressed.