Hi everyone!
I’m excited to announce SonarQube MCP Server v1.25.0.
This release builds on the improvements introduced in v1.24.0, making AI-assisted analysis more actionable while expanding support for Vortex-enabled organizations.
Whether you use the MCP server to bring SonarQube insights into AI assistants, support IDE workflows, or run Vortex-enabled analysis, these updates make the experience clearer, more flexible, and more resilient.
What’s New?
Vortex and IDE toolsets
Organizations entitled to Vortex can now activate a unified vortex toolset with SONARQUBE_TOOLSETS=vortex. The tools previously available through the analysis toolset remain accessible through this new entry point.
SonarQube for IDE bridge analysis tools, including analyze_file_list and toggle_automatic_analysis, are also now available through a dedicated ide toolset, making their purpose distinct from Vortex analysis workflows.
More actionable file-list analysis
The analyze_file_list tool now returns the rule key for every reported issue. This lets AI agents directly use get_rule_details to retrieve the relevant rule guidance, without needing additional context outside the analysis output.
Clearer Vortex analysis behavior
When the Vortex toolset is active, analyze_code_snippet is automatically disabled to ensure that the tool with most languages and issues covered is used in priority.
Improved Kubernetes reliability with HTTPS
This release fixes an HTTPS liveness-probe issue in Kubernetes. Previously, kubelet probes sent through a pod IP could trigger a 400 Invalid SNI response when TLS was enabled, leading to unnecessary pod restarts.
Getting Started
Update to SonarQube MCP Server v1.25.0 to access these improvements. If your organization is entitled to Vortex, set SONARQUBE_TOOLSETS=vortex to enable the unified Vortex toolset.
Happy coding!