Skip to main content
Glama
langtind

community-sonarcloud-mcp-server

by langtind

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SONARCLOUD_URLNoSonarCloud server URL (optional, defaults to https://sonarcloud.io)https://sonarcloud.io
SONARCLOUD_TOKENYesYour SonarCloud authentication token
SONARCLOUD_ORGANIZATIONYesYour SonarCloud organization key

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_issuesC

Search for issues in SonarCloud projects

get_measuresC

Get component measures/metrics

list_projectsA

List projects in the organization

get_pull_requestsB

List pull requests for a project

change_issue_statusC

Change the status of a SonarQube issue

list_languagesA

List all programming languages supported

search_metricsC

Search for available metrics

get_quality_gate_statusC

Get Quality Gate status for a project

list_quality_gatesB

List all quality gates

show_ruleA

Show detailed information about a rule

list_rule_repositoriesC

List rule repositories

get_raw_sourceC

Get source code as raw text

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 12 tools

Disambiguation4/5

Most tools target distinct resources and actions, such as listing quality gates versus getting a project's quality gate status. The only mild boundary is between search_metrics (metric catalog) and get_measures (actual metric values), but their descriptions make the distinction clear.

Naming Consistency3/5

The set mostly follows a lowercase verb_noun pattern but mixes verbs: list_, search_, get_, show_, and change_. For example, get_pull_requests could be list_pull_requests and show_rule could be get_rule, so the pattern is readable but not fully consistent.

Tool Count5/5

12 tools is well-scoped for a SonarCloud-focused server. Each tool covers a meaningful aspect of code quality analysis without feeling redundant or overwhelming.

Completeness4/5

The server covers core read-oriented workflows: projects, quality gates, issues, measures, metrics, rules, languages, pull requests, and source. Minor gaps exist, such as issue comments, project detail beyond listing, or quality gate management, but agents can accomplish common analysis tasks without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues