Paginated project finder; use when you need keys/names before running other SonarCloud tools.

Returns a list of projects with their keys and names, plus pagination information. Use the project keys returned here for other tools like search_sonar_issues_in_projects or search_hotspots.

Example: search_my_sonarqube_projects(page="1")

Return detailed metadata (qualifier, tags, branches) for a specific project/component.

Returns component information including name, qualifier (TRK for project, FIL for file, etc.), tags, and available branches. Use this to inspect project metadata or verify component existence.

Example: show_component(component="my-project", branch="main")

Traverse modules/files inside a project; supports paging, qualifier filters, and branch/PR context.

Returns a hierarchical view of project components (directories, files, modules). Use this to explore project structure or find specific files.

Example: component_tree(component="my-project", qualifiers=["FIL"], q="test", branch="main")

Search issues across one or more projects with optional PR, severity, and pagination controls.

Returns a list of issues matching the filters, with key details like rule, severity, component, and status. Use this to find code quality issues, bugs, vulnerabilities, or code smells in your projects.

Example: search_sonar_issues_in_projects(projects=["my-project"], severities="HIGH,BLOCKER", pullRequestId="123")

Discover SCM author accounts used in your org/project; useful for reviewer pickers or stats.

Returns a list of authors (from source control) who have contributed to issues in the organization or project. Requires SONARCLOUD_ORGANIZATION to be set.

Example: list_issue_authors(project="my-project", q="john")

Return the change history (status, assignee, severity edits) for the given issue key.

Returns a chronological list of all changes made to an issue, including who made the change and when. Useful for auditing issue lifecycle or understanding how an issue was resolved.

Example: get_issue_changelog(issue="AXabc123def456")

List available issue tags (optionally filtered by project or search query) to power tag selectors.

Returns a list of tags used on issues in the organization or project. Tags are custom labels that can be applied to issues for categorization.

Example: list_issue_tags(project="my-project", q="security")

Check whether a project/branch/PR passed its assigned quality gate and inspect failing conditions.

Returns the quality gate status (OK, ERROR, WARN, NONE) and details of any failing conditions. At least one of analysisId, projectId, or projectKey must be provided.

Quality gate status values:

• OK: All conditions passed

• ERROR: One or more conditions failed

• WARN: Warning threshold exceeded (deprecated)

• NONE: No quality gate set

Example: get_project_quality_gate_status(projectKey="my-project", pullRequest="123")

Enumerate all gates in the organization along with basic metadata and built-in flags.

Returns a list of all quality gates available in the organization, including their ID, name, and whether they are built-in or custom. Requires SONARCLOUD_ORGANIZATION to be set.

Example: list_quality_gates()

Fetch full gate definition (conditions, allowed actions) so LLMs can explain or compare them.

Returns detailed information about a specific quality gate, including all conditions (coverage thresholds, bug counts, etc.) and metadata. Requires SONARCLOUD_ORGANIZATION to be set. Either name or gate_id must be provided.

Example: show_quality_gate(name="Sonar way")

Page through projects associated with a gate; supports filtering by selection status and name.

Returns a list of projects and their association status with the specified quality gate. Useful for understanding which projects use which quality gates. Requires SONARCLOUD_ORGANIZATION to be set.

Example: search_quality_gates(gateId=123, selected=True, query="my-project")

Return the gate currently bound to a project so workflows can cross-reference status and rules.

Returns information about which quality gate is assigned to the specified project. Use this to determine what quality criteria a project must meet. Requires SONARCLOUD_ORGANIZATION to be set.

Example: get_quality_gate_by_project(project="my-project")

List hotspots for a project with optional file, branch, or PR filters; returns paging + summaries.

Security hotspots are security-sensitive pieces of code that need manual review. Returns a list of hotspots with their status, component, and vulnerability probability.

Hotspot status values:

• TO_REVIEW: Needs review

• REVIEWED: Has been reviewed (with resolution FIXED, SAFE, or ACKNOWLEDGED)

Example: search_hotspots(projectKey="my-project", branch="main", files="src/auth.java")

Return the full hotspot payload (rule, component, author, status) for a specific key.

Returns detailed information about a security hotspot, including the security rule that triggered it, the affected component/file, current status, resolution (if reviewed), and whether you can change its status.

Example: show_hotspot(hotspot="AXabc123def456")

Mark a hotspot TO_REVIEW or REVIEWED (with resolution) so downstream analyses see the new state.

This updates the status of a security hotspot after manual review.

Status values:

• TO_REVIEW: Mark the hotspot as needing review (no resolution required)

• REVIEWED: Mark as reviewed (resolution parameter is REQUIRED)

Resolution values (required when status=REVIEWED):

• FIXED: The vulnerability has been fixed

• SAFE: The code is safe and not actually a vulnerability

• ACKNOWLEDGED: The risk is acknowledged but accepted

Examples:

• Mark as reviewed and safe: change_hotspot_status(hotspot="AX123", status="REVIEWED", resolution="SAFE")

• Mark for review: change_hotspot_status(hotspot="AX123", status="TO_REVIEW")