Skip to main content
Glama
igorolv

sonar-mcp-server

by igorolv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to sonar-mcp-server

No user-submitted related servers found.

    Related Servers

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

    • 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
      21 PyPI
      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

    A4.3/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (get/list for project, issue, hotspot, rule, components, branches, PRs). The three issue-related tools are clearly differentiated: listIssues returns details, getProjectIssuesSummary returns aggregate facets, and getProjectIssuesBreakdown groups by module/rule.

    Naming Consistency5/5

    All tool names follow a consistent getX/listX pattern in camelCase, with nouns clearly indicating the resource. No mixing of conventions or vague verbs.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range and each tool covers a specific aspect of SonarQube analysis (projects, issues, hotspots, rules, branches, PRs, components). No redundancy or bloat.

    Completeness4/5

    Core read-only analysis workflows are well covered: project metrics, issue list/detail/snippets/aggregations, hotspot handling, and branch/PR scoping. Minor gaps include no listRules (only getRule) and no write actions (e.g., issue assignment or hotspot review), but these are not central to an analysis-focused server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources