# Windsurf [Windsurf](https://windsurf.com/) is an agentic IDE from Codeium. Use this MCP server setup when you want Sonar tools available within the Cascade AI agent in Windsurf. Windsurf lists the SonarQube MCP Server as a [security-focused extension](https://docs.windsurf.com/windsurf/recommended-plugins#security). If you prefer using a centrally managed MCP server, see [MCP server in SonarQube Cloud](#mcp-server-in-sonarqube-cloud). ## Use the configuration generator 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](/agent-centric-development-cycle/developer-tools/mcp-server/reference/environment-variables.md#common-variables). 3. Choose a [hosting method](/agent-centric-development-cycle/developer-tools/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. ## Manual setup ### Environment variables The following [common variables](/agent-centric-development-cycle/developer-tools/mcp-server/reference/environment-variables.md#common-variables) are required. Note that `SONARQUBE_TOKEN` applies to stdio transport only. For HTTP, HTTPS, or the embedded SonarQube Cloud 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. ### Transport options The SonarQube MCP Server supports three transport modes. Use [Stdio](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#local-server-stdio) for local development and most use cases, [HTTPS](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#https) for production and team deployments, and [HTTP](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#http) only on trusted internal networks. #### Stdio (recommended) Use [Stdio](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#local-server-stdio) for local development or when you are the only user. It's also the transport mode used in your [Agentic Analysis](/agent-centric-development-cycle/features/agentic-analysis.md) and [Context Augmentation](/agent-centric-development-cycle/features/context-augmentation.md) workflows. **Automatic MCP configuration** When you're using an AI-enabled IDE such as Cursor, Windsurf, or VS Code with Copilot enabled, and have already completed your [Connected mode setup](/sonarqube-for-vs-code/connect-your-ide/setup.md) in SonarQube for IDE with SonarQube Server or SonarQube Cloud, a quick select button is available. * Select the icon, **Configure MCP Server** from the **CONNECTED MODE** view window to use your connected mode credentials to start using the SonarQube MCP Server. The same workflow is available in the **AI AGENTS CONFIGURATION** view. If you've connected to a SonarQube Cloud organization in the US region, the configuration details will be shared. Watch the Windsurf and SonarQube MCP Server integration demo on YouTube. [Watch on YouTube](https://www.youtube.com/watch?v=bJoXEkwlBLc) > **Note:** Windsurf subscribers on Team and Enterprise plans should add the SonarQube MCP Server to the list of allowed servers. See the Windsurf documentation about [Admin Controls](https://docs.windsurf.com/plugins/cascade/mcp#admin-controls-teams-&-enterprises). **Manual configuration** The SonarQube MCP Server is available in the Windsurf MCP Marketplace for the [Cascade MCP client](https://docs.windsurf.com/windsurf/cascade/mcp). Follow these instructions: 1. Open Windsurf **Settings** > **Cascade** > **MCP Servers** and select **Open MCP Marketplace**. 2. Search for `sonarqube` on the Cascade MCP Marketplace. 3. Choose the **SonarQube MCP Server** and select **Install**. 4. Add the required SonarQube user token. Then add an organization key if you want to connect with SonarQube Cloud, or the SonarQube URL if you want to connect to SonarQube Server or SonarQube Community Build. > **Warning:** *User tokens* are required when setting up connected mode or an MCP Server between SonarQube Server and SonarQube for IDE. Note that binding won't function properly if *project tokens*, *global tokens*, or *scoped organization tokens* are used during the setup process. > **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](/agent-centric-development-cycle/developer-tools/mcp-server/setup/environment-considerations.md#connecting-to-sonarqube-cloud-in-the-us-region) section for details. #### HTTPS Use HTTPS when connecting Windsurf to a shared MCP server deployed for a team. This requires an [HTTPS transport server](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#https) to be running and accessible. Add the following to your Windsurf MCP configuration file: ```json { "mcpServers": { "sonarqube": { "type": "https", "url": "https://:8443/mcp", "headers": { "Authorization": "Bearer " } } } } ``` #### HTTP > **Important:** The [HTTP](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#http) transport mode is not recommended. Use [Stdio](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#stdio) for local development or [HTTPS](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#https) for multi-user production deployments. Use HTTP only on a trusted internal network or for local testing. This requires an [HTTP transport server](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#http) to be running. Add the following to your Windsurf MCP configuration file: ```json { "mcpServers": { "sonarqube": { "type": "http", "url": "http://:8080/mcp", "headers": { "Authorization": "Bearer " } } } } ``` ## Agentic analysis and context augmentation When using Agentic Analysis and Context Augmentation services, your `SONARQUBE_TOKEN` will allow your local MCP server configured for [Stdio](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#local-server-stdio) mode to authenticate to the SonarQube Cloud API. See [Agentic Analysis](/agent-centric-development-cycle/features/agentic-analysis.md) and [Context Augmentation](/agent-centric-development-cycle/features/context-augmentation.md) for more information. ## MCP Server in SonarQube Cloud Use the SonarQube Cloud-hosted MCP server to avoid running and maintaining your own MCP infrastructure while always using the current server version. The embedded server exposes a smaller, fixed subset of tools; for the available toolsets and configuration details, check SonarQube Cloud's [MCP Server in SonarQube Cloud](https://docs.sonarsource.com/sonarqube-cloud/ai-capabilities/sonarqube-mcp-server#mcp-server-in-sonarqube-cloud) page. *** ## Use Sonar tools from Windsurf Once connected, use the tools provided by the SonarQube MCP Server in Windsurf agent mode. See the [tools](/agent-centric-development-cycle/developer-tools/mcp-server/reference/tools.md) page for the full list of available tools. See also the [Windsurf documentation](https://docs.windsurf.com/context-awareness/windsurf-overview#chat-specific-context-features) for information on adding explicit context. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sonarsource.com/agent-centric-development-cycle/developer-tools/mcp-server/setup/quickstart-guides/windsurf.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.