Schema | sonarqube-api-mcp

sonarqube-api-mcp

Describes the environment variables required to run the server.

Name	Required	Description
`SONAR_TOKEN`	Yes	SonarQube token. Sent as Basic Auth using Authorization: Basic base64("${SONAR_TOKEN}:").
`SONAR_HOST_URL`	Yes	SonarQube base URL. Trailing slashes are normalized.
`SONAR_PROJECT_KEY`	No	Default project key used by project-scoped tools when projectKey and projectName are omitted.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
search_sonar_issuesC	Search read-only SonarQube issues through /api/issues/search.
get_quality_gate_statusC	Get read-only SonarQube quality gate status for a project.
get_rule_detailsC	Get read-only SonarQube rule details.
get_component_measuresC	Get read-only SonarQube component measures for metric keys.
get_sonar_sourcesA	Get read-only SonarQube source lines for a component.
search_sonar_projectsB	Find SonarQube project keys by project name or key.
get_sonar_issue_contextB	Get one SonarQube issue with source lines around the affected range.
get_sonar_fix_planA	Return unresolved SonarQube issues grouped by file with optional source context for fixing new-code or overall-code issues.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yozzone/sonarqube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server