sonarqube-mcp-server

A Model Context Protocol (MCP) server project intended to connect LLM agents to SonarQube/SonarCloud functionality. Based on provided README/repo metadata, the repository is archived and indicates it is no longer maintained.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ DevTools mcp sonarqube sonarcloud model-context-protocol developer-tools code-quality
⚙ Agent Friendliness
21
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
15
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
35
Documentation
10
Error Messages
0
Auth Simplicity
40
Rate Limits
0

🔒 Security

TLS Enforcement
50
Auth Strength
40
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
40

The provided content does not describe authentication, TLS requirements, secret management, or dependency posture. Because the repo is archived/unmaintained, security review and verification are required before using it in production.

⚡ Reliability

Uptime/SLA
0
Version Stability
20
Breaking Changes
20
Error Recovery
20
AF Security Reliability

Avoid When

Avoid using the archived/unmaintained MCP server in production unless you can audit and maintain it, or you migrate to the official referenced repository.

Use Cases

  • Letting an MCP-capable agent retrieve SonarQube/SonarCloud data (e.g., quality metrics, issues) to inform code review or remediation
  • Automating SonarQube insights into workflows such as incident triage, engineering reporting, and quality gate checks
  • Providing structured access for LLM tools rather than direct UI/API usage

Not For

  • A secure production integration without reviewing the archived codebase and authentication/authorization behavior
  • Use as a maintained dependency (repo is archived/unmaintained per provided README)
  • Organizations requiring documented SLAs, explicit support policies, or guaranteed compatibility across SonarQube versions

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication details were provided in the supplied README/metadata. SonarQube integrations typically use tokens/user auth, but this cannot be confirmed for this specific (archived) MCP server from the provided content.

Pricing

Free tier: No
Requires CC: No

No pricing information was provided; as an MCP server project, costs would generally be self-hosting and SonarQube access.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Repository is archived and explicitly described as unmaintained in the provided README, which increases the risk of protocol/tooling drift and broken integrations.
  • No information was provided about tool schemas, pagination, or rate limiting—agents may need custom handling once you inspect the code.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for sonarqube-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered