Skip to main content
Glama
sonarqube-mcp-py

sonarqube-mcp-py

by filhocf

sonarqube-mcp-py

A Python MCP server for SonarQube — query projects, issues, quality gates, coverage, and security hotspots directly from any MCP-compatible AI agent.

Inspired by the official SonarQube MCP Server (Java/Kotlin), reimplemented in Python for lightweight deployment without JVM dependency.

Install

uvx sonarqube-mcp-py
# or
pip install sonarqube-mcp-py

Related MCP server: sonar-mcp

Configuration

Set environment variables:

export SONARQUBE_URL=https://your-sonarqube-instance
export SONARQUBE_TOKEN=squ_your_token_here
export SONARQUBE_VERIFY_SSL=false  # optional, for self-signed certs

Transport

  • stdio (default): for mcp.json integration with Claude Desktop, Cursor, Kiro CLI, etc.

  • HTTP: set MCP_TRANSPORT=streamable-http and optionally MCP_PORT=8959

Available Tools

Tool

Description

search_sonarqube_projects

Search for projects

get_project_quality_gate_status

Get quality gate status (OK/ERROR)

get_component_measures

Get metrics (bugs, coverage, code smells, etc.)

list_quality_gates

List all quality gate definitions

search_sonar_issues

Search issues by severity and status

search_security_hotspots

Find security hotspots to review

show_security_hotspot

Get hotspot details

show_rule

Get rule description and examples

search_metrics

List all available metrics

list_pull_requests

List analyzed pull requests

get_file_coverage_details

Get per-file coverage data

search_files_by_coverage

Find files with lowest coverage

get_duplications

Get code duplication details

MCP Client Configuration

stdio (mcp.json)

{
  "sonarqube": {
    "command": "sonarqube-mcp-py",
    "env": {
      "SONARQUBE_URL": "https://your-instance",
      "SONARQUBE_TOKEN": "squ_xxx"
    }
  }
}

HTTP (standalone service)

{
  "sonarqube": {
    "url": "http://localhost:8959/mcp"
  }
}

Start in HTTP mode:

MCP_TRANSPORT=streamable-http MCP_PORT=8959 sonarqube-mcp-py

License

MIT

Available Tools

13 tools
get_component_measuresC

Get metrics for a component (bugs, coverage, etc.)

Inputs: component (required), metric_keys (required), branch.

get_duplicationsC

Get code duplications for a file

Inputs: file_key (required), branch.

get_file_coverage_detailsC

Get coverage details for files in a project

Inputs: component (required), page_size, branch.

get_project_quality_gate_statusC

Get quality gate status for a project

Inputs: project_key (required), branch.

list_pull_requestsC

List pull requests analyzed for a project

Inputs: project_key (required).

list_quality_gatesA

List all quality gates defined in SonarQube

Inputs: no named parameters.

search_files_by_coverageD

Find files with lowest coverage

Inputs: component (required), page_size, branch.

search_metricsA

List all available metrics in SonarQube

Inputs: no named parameters.

search_security_hotspotsC

Search for security hotspots in a project

Inputs: project_key (required), status, branch.

search_sonar_issuesC

Search for issues (bugs, vulnerabilities, code smells) in a project

Inputs: project_key (required), severities, statuses, page_size, +1 more.

search_sonarqube_projectsC

Search for projects in SonarQube

Inputs: query, page_size.

show_ruleC

Get details of a SonarQube rule

Inputs: rule_key (required).

show_security_hotspotC

Get details of a specific security hotspot

Inputs: hotspot_key (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    13 tools is well-scoped for a SonarQube server, covering core inspection and analysis functionalities without being overwhelming. Each tool earns its place.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for SonarQube that enables LLM agents to discover projects, analyze code quality metrics, check Quality Gate status, search issues with filters, and rank projects by worst-performing metrics. It provides read-only, safe access to SonarQube instances with structured outputs and error handling.
      5
      90 PyPI
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes SonarQube data as AI agent tools, enabling project discovery, quality gates, measures, issues, hotspots, rule explanations, source code, and raw API access.
      4
      -