> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/agent-centric-development-cycle/developer-tools/agent-plugins/kiro.md).

# Kiro

Install the SonarQube Power in Kiro to bring SonarQube code quality and security analysis into your AI coding sessions.

The SonarQube Power for Kiro connects Amazon's AI coding IDE to SonarQube's code quality and security features. The Power works with SonarQube Cloud or SonarQube Server.

## Features

The Power gives Kiro's agent access to the full set of [Tools](https://docs.sonarsource.com/sonarqube-mcp-server/reference/tools.md) exposed by the SonarQube MCP Server, including:

* Code analysis: analyze code snippets and files in the agent context.
* Issues: search, review, and update code issues.
* Quality gates: check the quality gate status for a project.
* Security hotspots: search and review security hotspots.
* Coverage: find under-covered files and review line-by-line coverage.
* Dependencies: check third-party dependencies for SCA issues.

> **Note:** The Kiro Power does not install hooks, so secrets detection, Vortex analysis, and Vortex context are not configured automatically. You can still access each one:
>
> * **Secrets detection**: Secrets detection is built into the SonarQube CLI. After installing the CLI as directed during Power setup, run `sonar analyze secrets <path>` from your terminal.
> * **Vortex analysis**: Available through the SonarQube MCP Server with the `vortex` toolset enabled and your workspace mounted. See [Vortex with the MCP server](https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides/install-vortex-with-mcp.md#step-2-add-or-edit-your-mcp-configuration-file) for toolset setup steps.
> * **Vortex context**: Requires a local MCP Server running in a container runtime with a volume mount and the `vortex` toolset. See [Vortex with the MCP server](https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides/install-vortex-with-mcp.md#step-2-add-or-edit-your-mcp-configuration-file) for toolset setup steps.

## Prerequisites

* A SonarQube Cloud organization or SonarQube Server instance.
* [Kiro](https://kiro.dev/) installed.
* The SonarQube CLI. Kiro will guide you through the installation as part of your Power setup. The MCP Server uses your `sonar auth login` session to connect.

## Install

The SonarQube Power is published on the [Kiro Powers marketplace](https://kiro.dev/powers/). Find **SonarQube** and click **Add to Kiro**. The MCP Server configuration is applied automatically.

## Configuration

Log in so the MCP Server can connect:

```bash
sonar auth login
```

Use the command for your scenario:

| Scenario             | Command                                                             |
| -------------------- | ------------------------------------------------------------------- |
| SonarQube Cloud (EU) | `sonar auth login -o <YourOrganizationKey>`                         |
| SonarQube Cloud (US) | `sonar auth login -o <YourOrganizationKey> -s https://sonarqube.us` |
| SonarQube Server     | `sonar auth login -s <YourServerURL>`                               |

Your browser opens to complete login, and the token is stored in your system keychain. Check your authentication anytime with `sonar auth status`.

## Verify that it works

In Kiro's chat, ask: *"List my SonarQube projects."* Kiro should call the SonarQube MCP Server and return your project list. If it does not, check Kiro's MCP settings to confirm the SonarQube Power is enabled, then run `sonar auth status` to confirm the underlying token is healthy and restart Kiro.

### Test Sonar Vortex

To confirm that Vortex analysis and context are both working, see [Checking that Vortex works properly](https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides/check-vortex-setup.md).

## Related pages

* [Kiro Powers marketplace](https://kiro.dev/powers/)
* [SonarQube MCP Server in Kiro](https://docs.sonarsource.com/sonarqube-mcp-server/setup/quickstart-guides/kiro.md)
* [Sonar Vortex context](https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-context.md)
* [Sonar Vortex analysis](https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-analysis.md)
* [Vortex for Kiro](https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides/install-vortex-kiro.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/agent-centric-development-cycle/developer-tools/agent-plugins/kiro.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
