> 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/sonarqube-mcp-server/setup/quickstart-guides/codex-cli.md). # Codex CLI Set up the SonarQube MCP Server with Codex CLI and start using Sonar tools with your agent. [Codex CLI](https://github.com/openai/codex) is OpenAI's terminal-based AI coding assistant. Use this MCP server setup when you want to use Sonar tools from within a Codex CLI workflow. ## Choose your setup The SonarQube MCP Server lets an AI agent query your SonarQube projects. With it, Codex CLI can look up issues, quality gates, and coverage while it works. You can use a server that SonarQube hosts, run your own, or have the SonarQube CLI set it up for you. Choose how to connect: | Option | Is best for | What you get | Who sets it up | | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------- | | [Automated setup](#automated-setup-with-the-sonarqube-cli) | Automatic configuration in Codex CLI | The MCP server, secrets detection, and Sonar Vortex analysis and context | You | | [SonarQube Cloud-hosted](#connect-to-a-sonarqube-hosted-mcp-server) | SonarQube Cloud users | Nothing to install and a smaller, fixed subset of tools. No Sonar Vortex. | You connect | | [SonarQube Server-hosted](#connect-to-a-sonarqube-hosted-mcp-server) | SonarQube Server 2026.3 and later (Developer, Enterprise, and Data Center editions) | Nothing to install on your machine. No Sonar Vortex. | An administrator installs it, and then you connect | | [Self-hosted MCP server](#set-up-a-self-hosted-mcp-server) | Full control | The MCP server that you run yourself, with the Sonar Vortex analysis and context tools through the Stdio transport | You | For any option except the automated setup, the [configuration generator](https://mcp.sonarqube.com/config-generator.html) gives you a snippet to paste into your `~/.codex/config.toml` file. ## Automated setup with the SonarQube CLI To skip manual configuration, use the [Codex CLI setup flow](/sonarqube-cli/integrations/codex.md). It configures the MCP server automatically and also adds secrets detection, Vortex analysis, and Vortex context. Set up Vortex analysis and Vortex context using the SonarQube plugin or SonarQube CLI. See [Sonar Vortex analysis](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-analysis.md) and [Sonar Vortex context](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-context.md). ## Connect to a SonarQube-hosted MCP server Connect to a SonarQube-hosted MCP server to skip running your own MCP infrastructure and always use the current server version: * SonarQube Cloud-hosted: for SonarQube Cloud users. The MCP server is embedded in SonarQube Cloud, so there's nothing to install, and it exposes a smaller, fixed subset of tools. To connect, see the [SonarQube Cloud-hosted](/sonarqube-mcp-server/setup/sonarqube-cloud-hosted.md) page. * SonarQube Server-hosted: for SonarQube Server users on Developer, Enterprise, and Data Center editions, version 2026.3 and newer. An administrator installs the MCP server extension on your instance, and then you [connect your AI agent](/sonarqube-mcp-server/setup/sonarqube-server-hosted.md#connect-your-ai-agent). To install the extension, see the [SonarQube Server-hosted](/sonarqube-mcp-server/setup/sonarqube-server-hosted.md#install-the-mcp-server) page. Neither the SonarQube Cloud-hosted nor the SonarQube Server-hosted option supports Sonar Vortex, which requires local filesystem access. To use Sonar Vortex, use the automated setup or a self-hosted MCP server. To get the connection snippet for either option, use the [configuration generator](https://mcp.sonarqube.com/config-generator.html) and select the matching hosting method. ## Set up a self-hosted MCP server A self-hosted MCP server runs on your machine or in your own environment, and you manage it yourself. ### Before you start The following [common variables](/sonarqube-mcp-server/reference/environment-variables.md#common-variables) are required. `SONARQUBE_TOKEN` applies to stdio transport only. For HTTP, HTTPS, or the SonarQube Cloud-hosted MCP server, use the `Authorization: Bearer ` header instead. * `SONARQUBE_TOKEN`: Your SonarQube user token (stdio transport). * `SONARQUBE_ORG`: Your SonarQube Cloud organization key. Required for SonarQube Cloud only. * `SONARQUBE_URL`: Your SonarQube Server or Community Build URL. Also required for SonarQube Cloud in the US region (`https://sonarqube.us`). Not needed for SonarQube Cloud in the EU region. > **Important:** Your SonarQube token is a sensitive credential. Use environment variables to pass tokens rather than hardcoding them in configuration files. Never commit tokens to version control. > **Warning:** *User tokens* are required when setting up connected mode or your SonarQube MCP server with SonarQube (Server, Cloud). Your binding will not function properly if you use *project tokens*, *global tokens*, or *scoped organization tokens* during setup. When using these features, your `SONARQUBE_TOKEN` lets your local MCP server configured for [Stdio](/sonarqube-mcp-server/setup/self-hosted.md#local-server-stdio) mode authenticate to the SonarQube Cloud API. See [Sonar Vortex analysis](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-analysis.md) and [Sonar Vortex context](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-context.md). ### Configure manually The SonarQube MCP Server supports three transport modes. Use [Stdio](/sonarqube-mcp-server/setup/self-hosted.md#local-server-stdio) for local development and most use cases, [HTTPS](/sonarqube-mcp-server/setup/self-hosted.md#https-streamable-http-over-tls) for production and team deployments, and [HTTP](/sonarqube-mcp-server/setup/self-hosted.md#http-streamable-http) only on trusted internal networks. Use the official [SonarQube MCP Server configuration generator](https://mcp.sonarqube.com/config-generator.html) to get a configuration code snippet for your setup: 1. Identify the target MCP Client. 2. Find your [#common-variables](/sonarqube-mcp-server/reference/environment-variables.md#common-variables). 3. Choose a [hosting method](/sonarqube-mcp-server/setup/environment-considerations.md#hosting-method). 4. Enter the information into the configuration generator. 5. Paste the generated configuration into your configuration file. To configure by hand instead, select a transport tab. {% tabs %} {% tab title="STDIO (RECOMMENDED)" %} Use [Stdio](/sonarqube-mcp-server/setup/self-hosted.md#local-server-stdio) for local development or when you're the only user. It's also the transport mode used in your [Sonar Vortex analysis](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-analysis.md) and [Sonar Vortex context](/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex-context.md) workflows. In your `~/.codex/config.toml` file, add the following configuration: > **Note:** This code sample configures the MCP server using [Stdio](/sonarqube-mcp-server/setup/self-hosted.md#local-server-stdio) transport, where `SONARQUBE_TOKEN` is passed as an environment variable. > > For [HTTPS](/sonarqube-mcp-server/setup/self-hosted.md#https-streamable-http-over-tls), [HTTP](/sonarqube-mcp-server/setup/self-hosted.md#http-streamable-http), or the [SonarQube-hosted MCP server](#connect-to-a-sonarqube-hosted-mcp-server), the `SONARQUBE_TOKEN` header is deprecated. Pass the token using the `"Authorization": "Bearer "` header instead. > **Note:** SONARQUBE\_URL should be defined as `https://sonarqube.us` each time you use a SonarQube Cloud configuration (`SONARQUBE_TOKEN` + `SONARQUBE_ORG`) and want to connect to a US-region instance. See the [Connecting to SonarQube Cloud in the US region](/sonarqube-mcp-server/setup/environment-considerations.md#connecting-to-sonarqube-cloud-in-the-us-region) section for details. > **Note:** Docker's MCP Hub publishes the [`mcp/sonarqube`](https://hub.docker.com/r/mcp/sonarqube) image on its own cadence, so it may occasionally lag behind the latest release. The examples below use [`sonarsource/sonarqube-mcp`](https://hub.docker.com/r/sonarsource/sonarqube-mcp/tags) instead, which receives new releases first and supports versioned tags for stable pinning. **Codex CLI with SonarQube Cloud** ```toml [mcp_servers.sonarqube] command = "docker" args = ["run", "--rm", "-i", "--init", "--pull=always", "-e", "SONARQUBE_TOKEN", "-e", "SONARQUBE_ORG", "sonarsource/sonarqube-mcp"] env = { "SONARQUBE_TOKEN" = "", "SONARQUBE_ORG" = "" } # For SonarQube Cloud in the US region, replace the args and env lines with these two lines: # args = ["run", "--rm", "-i", "--init", "--pull=always", "-e", "SONARQUBE_TOKEN", "-e", "SONARQUBE_ORG", "-e", "SONARQUBE_URL", "sonarsource/sonarqube-mcp"] # env = { "SONARQUBE_TOKEN" = "", "SONARQUBE_ORG" = "", "SONARQUBE_URL" = "https://sonarqube.us" } ``` **Codex CLI with SonarQube Server** ```toml [mcp_servers.sonarqube] command = "docker" args = ["run", "--rm", "-i", "--init", "--pull=always", "-e", "SONARQUBE_TOKEN", "-e", "SONARQUBE_URL", "sonarsource/sonarqube-mcp"] env = { "SONARQUBE_TOKEN" = "", "SONARQUBE_URL" = "" } ``` > **Tip:** To verify the connection, ask your AI agent to call the SonarQube MCP `ping_system` tool. For example: *"Ping the SonarQube MCP server."* > **Note:** Restart Codex CLI for the new MCP server configuration to take effect. > {% endtab %} {% tab title="HTTPS" %} Use HTTPS when connecting Codex CLI to a shared MCP server deployed for a team. This requires an [HTTPS transport server](/sonarqube-mcp-server/setup/self-hosted.md#https-streamable-http-over-tls) to be running and accessible. Add the following to your `~/.codex/config.toml` file: ```toml [mcp_servers.sonarqube] type = "https" url = "https://:8443/mcp" headers = { "Authorization" = "Bearer " } ``` > **Tip:** To verify the connection, ask your AI agent to call the SonarQube MCP `ping_system` tool. For example: *"Ping the SonarQube MCP server."* > **Note:** Restart Codex CLI for the new MCP server configuration to take effect. > {% endtab %} {% tab title="HTTP" %} > **Important:** The [HTTP](/sonarqube-mcp-server/setup/self-hosted.md#http-streamable-http) transport mode is not recommended. Use [Stdio](/sonarqube-mcp-server/setup/self-hosted.md#stdio) for local development or [HTTPS](/sonarqube-mcp-server/setup/self-hosted.md#https-streamable-http-over-tls) for multi-user production deployments. Use HTTP only on a trusted internal network or for local testing. This requires an [HTTP transport server](/sonarqube-mcp-server/setup/self-hosted.md#http-streamable-http) to be running. Add the following to your `~/.codex/config.toml` file: ```toml [mcp_servers.sonarqube] type = "http" url = "http://:8080/mcp" headers = { "Authorization" = "Bearer " } ``` > **Tip:** To verify the connection, ask your AI agent to call the SonarQube MCP `ping_system` tool. For example: *"Ping the SonarQube MCP server."* > **Note:** Restart Codex CLI for the new MCP server configuration to take effect. > {% endtab %} > {% endtabs %} ## Use Sonar tools from Codex CLI Once connected, Codex CLI can call SonarQube MCP tools on your behalf. See the SonarQube MCP [Tools](/sonarqube-mcp-server/reference/tools.md) page for the full list of available tools. --- # 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/sonarqube-mcp-server/setup/quickstart-guides/codex-cli.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.