Environment
- SonarQube Cloud
- Deployment type (STDIO/HTTP, Docker/JAR): -
- Client / AI tool using MCP (if applicable): Claude Code
Description
I’d like to request that SonarSource publish an MCP server for SonarCloud that’s fully compliant with the current Model Context Protocol specification, including the OAuth 2.1 authorization flow for remote servers.
Current state
The endpoint exists at https://api.sonarcloud.io/mcp, but it doesn’t support the MCP authorization spec - connecting it to Claude.ai’s connector system fails.
Why this matters
MCP is becoming the standard for connecting AI assistants to external tools. Integration with SonarCloud is already possible (via API tokens or self-hosted MCP servers), but a spec-compliant hosted server with OAuth would make it significantly more accessible - users could connect with a single click, no token management required.
This would enable seamless integration with:
- Claude (via Connectors Directory), also Claude Code on the web, using the centrally configured mcp
- Cursor, Windsurf, Cline, and other AI coding tools
- Any future MCP-compatible assistant
Request
Update the existing MCP endpoint to support MCP Authorization (OAuth 2.1) and submit to the Claude Connectors Directory.