Skip to main content
Glama
yasojha

sonarqube-api-mcp

by yasojha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to sonarqube-api-mcp

No user-submitted related servers found.

    Related Servers

    • SonarQube MCP Server

      anggakawa
      F
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that provides AI assistants with structured access to SonarQube projects, issues, metrics, and rules. It enables safe analysis of code quality and security findings through a set of validated, safety-first tools.
      6
      -

    • sonarqube-mcp

      metalralf
      F
      license
      Not graded
      quality
      A
      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
      -

    • sonarqube-mcp

      mshegolev
      A
      license
      A
      quality
      B
      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
      51 PyPI
      MIT

    • sonarqube-mcp-py

      filhocf
      A
      license
      C
      quality
      D
      maintenance
      A Python MCP server for SonarQube, enabling AI agents to query projects, issues, quality gates, coverage, and security hotspots.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of SonarQube (measures, quality gate, rules, issues, sources, projects) with no overlapping purposes. An agent can clearly differentiate between them.

    Naming Consistency3/5

    Tools mostly follow a verb_noun pattern, but there is inconsistency in the use of the 'sonar' prefix: some include it (get_sonar_fix_plan) while others do not (get_component_measures). This mixed style reduces clarity.

    Tool Count5/5

    Eight tools is well-scoped for a SonarQube API server, covering the core read operations without being excessive or insufficient.

    Completeness4/5

    The tool surface covers essential read-only operations (measures, quality gate, rules, issues, sources, projects). Minor gaps like a dedicated list_rules tool are present, but agents can work around using search_sonar_issues.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources