> 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/deprecations-and-removals.md).

# 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](/sonarqube-mcp-server/reference/environment-variables.md#common-variables) for more detail.

`SONARQUBE_TOKEN` as an HTTP header is deprecated for Streamable HTTP transport.

* When connecting clients via [HTTP (Streamable HTTP)](/sonarqube-mcp-server/setup/self-hosted.md#http-streamable-http) or [HTTPS (Streamable HTTP over TLS)](/sonarqube-mcp-server/setup/self-hosted.md#https-streamable-http-over-tls), use the `Authorization: Bearer <YourSonarQubeUserToken>` header instead. This is mandatory for the [SonarQube Cloud-hosted MCP server](/sonarqube-mcp-server/setup/sonarqube-cloud-hosted.md), and recommended for all other Streamable HTTP configurations.
* For [Stdio](/sonarqube-mcp-server/setup/self-hosted.md#local-server-stdio) transport, `SONARQUBE_TOKEN` as an environment variable is unchanged.

The older SSE-only HTTP transport from earlier MCP versions is deprecated and not supported. Use **Streamable HTTP** (`SONARQUBE_TRANSPORT=http` or `https`) instead.

`branchKey`, `pullRequestKey`, and `pullRequestId` are deprecated in SonarQube MCP Server version 1.20.

* Replaced by `branch` and `pullRequest` on the affected tools. Use `list_branches` and `list_pull_requests` to discover valid values. See [Branch and pull request context](/sonarqube-mcp-server/reference/tools.md#branch-and-pull-request-context) for usage guidance.

### Removed parameters

Legacy pagination and project-filter parameter names were removed in SonarQube MCP Server version 1.23.

* `p` and `ps` were replaced by `pageIndex` and `pageSize` on `search_sonar_issues_in_projects`, `search_security_hotspots`, and `search_metrics`.
* `page` was replaced by `pageIndex` on `search_my_sonarqube_projects`. Use `pageSize` to control result count.
* `projects` was replaced by `projectKeys` on `search_sonar_issues_in_projects`.
* `branchName` was replaced by `branch` on `run_advanced_code_analysis`.

See [Tools](/sonarqube-mcp-server/reference/tools.md) for the canonical parameter names.

`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/verify/sonar-vortex-agentic-analysis.md) is enabled for your organization; no environment variable is required.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-mcp-server/deprecations-and-removals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.