Skip to main content
Glama
filhocf

sonarqube-mcp-py

by filhocf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to sonarqube-mcp-py

No user-submitted related servers found.

    Related Servers

    • sonarqube-mcp

      metalralf
      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
      -

    • 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
      MIT

    • community-sonarcloud-mcp

      langtind
      A
      license
      B
      quality
      D
      maintenance
      A lightweight TypeScript MCP server that provides AI assistants with seamless access to SonarCloud data, enabling code quality metrics, issues, and project queries.
      12
      306 npm
      MIT

    • sonar-mcp-server

      igorolv
      A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server for self-hosted SonarQube Community Build 26.4+: lets AI agents (Claude Code, Cursor, Copilot) read issues, security hotspots, rules and code snippets to fix findings locally
      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

    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
    ResponsivenessResponsive

    Resources