# Deprecations and removals

This page lists deprecated and removed parameters for the SonarQube MCP Server.

## Deprecation announcements

### Deprecated parameters

`SONARQUBE_CLOUD_URL` is deprecated in SonarQube MCP Server version 1.9.

* Replaced by `SONARQUBE_URL`, which works for SonarQube Server and SonarQube Cloud URLs, including the US region. See [#common-variables](/agent-centric-development-cycle/developer-tools/mcp-server/reference/environment-variables.md#common-variables) for more detail.

`SONARQUBE_TOKEN` as an HTTP header is deprecated for HTTP and HTTPS transport.

* When connecting clients via [HTTP](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#http) or [HTTPS](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#https) transport, use the `Authorization: Bearer <YourSonarQubeUserToken>` header instead. This is mandatory for the embedded [SonarQube Cloud](broken://spaces/B4UT2GNiZKjtxFtcFAL7/pages/ihYiNZvJQv7d8WYW3W84) MCP configuration, and recommended for all other HTTP(S) configurations.
* For [Stdio](/agent-centric-development-cycle/developer-tools/mcp-server/setup/self-hosted.md#local-server-stdio) transport, `SONARQUBE_TOKEN` as an environment variable is unchanged.

### Removed parameters

`SONARQUBE_ADVANCED_ANALYSIS_ENABLED` was removed in SonarQube MCP Server version 1.13.

* Replaced by a SonarQube Cloud organization level feature flag. The MCP Server now automatically detects whether [agentic-analysis.md](/agent-centric-development-cycle/features/agentic-analysis.md) is enabled for your organization; no environment variable is required.


---

# 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/deprecations-and-removals.md?ask=<question>
```

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.