Skip to main content
Glama
anggakawa

SonarQube MCP Server

by anggakawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SonarQube MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

      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
      -

    • 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

    • MCQuest MCP

      LionTechSupport
      F
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that gives AI coding agents structured access to a project's source code, architecture, documentation, and Git context through 16 tools for searching, reading, and comparing evidence without modifying files.
      16
      -
    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

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: connectivity check, single issue retrieval, project metrics, rule details, project listing, and issue searching. The descriptions specify different resources (server, issue, project, rule) and actions (check, get, list, search), making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., check_status, get_issue, list_projects, search_issues). The verbs are appropriate and predictable, with no deviations in style or convention across the set.

    Tool Count5/5

    Six tools is well-scoped for a SonarQube server, covering core functionalities like status verification, issue and project management, metrics, and rule lookup. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness4/5

    The toolset provides strong coverage for querying and monitoring in SonarQube, including status, projects, issues, metrics, and rules. A minor gap exists in write operations (e.g., creating or resolving issues), but agents can still perform most read-oriented tasks effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources