> 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/inside-your-agent-the-agentic-loop/how-to-guides/install-vortex-kiro.md). # Vortex for Kiro How to install Vortex for Kiro using the SonarQube Power and the SonarQube MCP Server. For Kiro, Vortex runs through the SonarQube MCP Server. The SonarQube Power installs the MCP Server configuration for you, and you then enable the toolsets Vortex needs. The SonarQube CLI has no `sonar integrate kiro` command, so the plugin-plus-CLI path available for other agents does not apply here. ## Prerequisites * The [general prerequisites for Vortex](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides/vortex-prerequisites.md). * The requirements for running Vortex through MCP, including a Docker-compatible installation. See [Prerequisites](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides/install-vortex-with-mcp.md#prerequisites) on the MCP page. ## Step 1: Install the SonarQube Power for Kiro 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. For more details, see [Kiro](/agent-centric-development-cycle/developer-tools/agent-plugins/kiro.md). ## Step 2: Authenticate Log in so the MCP Server can connect: ```bash sonar auth login ``` ## Step 3: Enable the Vortex toolsets The Power does not enable the toolsets Vortex needs. Edit your MCP configuration to add them, as described in [Add or edit your MCP configuration file](/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). ## Step 4: Restart your agent If Kiro is already running, restart it so the configuration is loaded for the current project. ## Step 5: Verify your setup Ask your agent *"What is the current architecture of the project? Limit the answer to the top-level blocks."* For the expected response, see [Checking your setup](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/how-to-guides/check-vortex-setup.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/inside-your-agent-the-agentic-loop/how-to-guides/install-vortex-kiro.md?ask=&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.