---
title: "Kiwi for SonarQube"
description: "Have the agent on a Kiwi step read the SonarQube quality gate and issues for its change through the SonarQube MCP server."
canonical: "https://kiwiflow.io/integrations/sonarqube"
---

# Kiwi for SonarQube

Have the agent on a Kiwi step read the SonarQube quality gate and issues for its change through the SonarQube MCP server.

- Your agent works in SonarQube through its own connection. Kiwi does not call SonarQube and never holds its credentials.
- A workflow skill can list SonarQube among the tools it requires. When you supply your agent's available tools to a skill check and SonarQube is not among them, the check reports `SK15-UNSUPPORTED-TOOL`.
- A project Admin can add links to SonarQube, with notes, under Connections and bind them to the steps that use them. The agent reads them with `list_connections`.
- The agent can report the tools and plugins it ran with, including its SonarQube connection, with `report_configuration`.
- The agent submits links to its work in SonarQube as the step's outputs. People review them, and sign-off stays with the people your workflow names.

## What your agent can do in SonarQube

- Read the quality gate status of a project or pull request.
- Search a project's issues and change an issue's status.
- Read measures such as coverage, and the security hotspots that need review.
- Analyze a code snippet or file before it is committed.
- List the pull requests that SonarQube has analyzed for a project.

## Set up

### 1. Connect your agent to Kiwi

Add Kiwi's hosted MCP server, `https://kiwiflow.io/mcp`, to your coding agent.

- [Coding agents](https://kiwiflow.io/integrations#agent)
- [Quickstart](https://docs.kiwiflow.io/quickstart#connect-your-agent)

### 2. Connect your agent to SonarQube

Run the SonarQube MCP server where your agent runs. The credentials stay with your agent.

```
docker run -i --rm --init --pull=always -e SONARQUBE_TOKEN -e SONARQUBE_URL sonarsource/sonarqube-mcp
```

- [SonarQube documentation](https://docs.sonarsource.com/sonarqube-mcp-server/setup/quickstart-guides/claude-code)

### 3. Example skill

Publish instructions like these as a workflow skill that lists SonarQube among its required tools.

```
Start from the SonarQube project key and the pull request in the assignment.
Read the quality gate and fix the issues that fail it in the code.
Leave issue statuses alone; the assigned reviewer decides on exceptions.
Submit the quality gate result and the fixed issue keys as outputs.
If the gate still fails after one round of fixes, stop and report a
blocker to the step owner with the remaining issues.
```

## More code quality and security integrations

- [Kiwi for Snyk](https://kiwiflow.io/integrations/snyk.md): Have the agent on a Kiwi step scan its code and dependencies for vulnerabilities through the MCP server in the Snyk CLI.
- [Kiwi for Codecov](https://kiwiflow.io/integrations/codecov.md): Have the agent on a Kiwi step read a pull request's coverage change from the Codecov API and return it with the step's outputs.
- [Kiwi for Semgrep](https://kiwiflow.io/integrations/semgrep.md): Have the agent on a Kiwi step scan the code it changed for security issues with Semgrep through the Semgrep CLI's MCP server.
- [Kiwi for CodeRabbit](https://kiwiflow.io/integrations/coderabbit.md): Have the agent on a Kiwi step review its own changes with the CodeRabbit CLI and fix the findings before it submits them.
- [Kiwi for Socket](https://kiwiflow.io/integrations/socket.md): Have the agent on a Kiwi step check the Socket scores of a dependency before adding it, through Socket's MCP server.

- [Get started](https://kiwiflow.io/get-started)
- [Read the setup guide](https://docs.kiwiflow.io/other-tools)