# Strange OAuth Problem **URL:** \ **Category:** SonarQube MCP Server\ **Created:** [April 9, 2026, 7:16am UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948 "2026-04-09T07:16:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![SSindelar](https://avatars.discourse-cdn.com/v4/letter/s/cdc98d/32.png) [@SSindelar](https://community.sonarsource.com/u/SSindelar)\ **Post date:** [April 9, 2026, 7:16am UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948/1 "2026-04-09T07:16:39Z")
### Environment - SonarQube Server or Cloud? Server - Deployment type (STDIO/HTTP, Docker/JAR): HTTP Docker - Client / AI tool using MCP (if applicable): Github Copilot (CLI & Eclipse ### Description I’m trying to setup the Sonarqube MCP Server to be used by multiple people/agents. I have it running in a docker container in HTTP mode. docker compose file: ```yaml services: sonarqube-mcp: init: true pull_policy: always ports: - 18080:18080 environment: - SONARQUBE_TRANSPORT=http - SONARQUBE_HTTP_PORT=18080 - SONARQUBE_TOKEN=squ_xxxxxx - SONARQUBE_URL=http://xxxxx:9000/ - SONARQUBE_HTTP_HOST=0.0.0.0 image: mcp/sonarqube ``` The server starts without an issues and downloads everything from our Sonarqube server. But when I try to connect to it I get redirected to a not working OAuth authentication. From what I have gathered the OAuth authentication is currently getting implemented and shouldn’t be part of the current docker image. ```json "sonarqube-http": { "url": "http://localhost:18080/mcp", "headers": { "Authorization": "Bearer squ_xxxxx" } } ``` Using the server in stdio mode works fine. ```json "sonarqube": { "command": "docker", "args": [ "run", "--init", "--pull=always", "-i", "--rm", "-e", "SONARQUBE_TOKEN", "-e", "SONARQUBE_URL", "-e", "SONARQUBE_IDE_PORT", "mcp/sonarqube" ], "env": { "SONARQUBE_TOKEN": "squ_xxxxx", "SONARQUBE_URL": "http://xxxxxxx:9000/", "SONARQUBE_IDE_PORT": "64120" } } ``` Any idea what causes this strange behavior? ---
**Author:** ![nicolas.quinquenel](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/nicolas.quinquenel/32/40740_2.png) [@nicolas.quinquenel](https://community.sonarsource.com/u/nicolas.quinquenel)\ **Post date:** [April 13, 2026, 8:38am UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948/4 "2026-04-13T08:38:47Z")
Hey @SSindelar, thanks for reaching out! OAuth is indeed not yet supported, but our MCP shouldn’t even try to load this logic. If you see a problem regarding OAuth, it’s likely your MCP client that is trying this setup. Checking the Copilot CLI [documentation](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers#editing-the-configuration-file), could you make sure that you’re adding this key/value in your configuration: ```auto "type": "http", "tools": ["*"] ``` ---
**Author:** ![bmarotta-ease](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/bmarotta-ease/32/37226_2.png) [@bmarotta-ease](https://community.sonarsource.com/u/bmarotta-ease)\ **Post date:** [September 1, 2026, 10:01am UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948/6 "2026-09-01T10:01:01Z")
When do you plan to implement OAuth? ---
**Author:** ![nicolas.quinquenel](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/nicolas.quinquenel/32/40740_2.png) [@nicolas.quinquenel](https://community.sonarsource.com/u/nicolas.quinquenel)\ **Post date:** [September 1, 2026, 12:24pm UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948/7 "2026-09-01T12:24:00Z")
Hey @bruna_gabutti, OAuth support for our MCP is in our roadmap. I can’t tell you exactly when it will be released, but it’s coming soon. Thanks for your patience! ---
**Author:** ![mohamad-alhusseinie](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/mohamad-alhusseinie/32/77512_2.png) [@mohamad-alhusseinie](https://community.sonarsource.com/u/mohamad-alhusseinie)\ **Post date:** [September 15, 2026, 1:10pm UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948/8 "2026-09-15T13:10:50Z")
Is there maybe a way to track this/get notified when it is done. Our company has a constraint to only use mcps via oauth. ---
**Author:** ![Farah](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/farah/32/60691_2.png) [@Farah](https://community.sonarsource.com/u/Farah)\ **Post date:** [September 16, 2026, 7:33am UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948/10 "2026-09-16T07:33:00Z")
Hi @mohamad-alhusseinie, unfortunately not but it is well on top of our priority list. You should expect it to be ready in a couple of month the latest and we’ll update the thread once it’s released. Are you on SonarQube Cloud or Server? Thank you for your patience. ---
**Author:** ![mohamad-alhusseinie](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/mohamad-alhusseinie/32/77512_2.png) [@mohamad-alhusseinie](https://community.sonarsource.com/u/mohamad-alhusseinie)\ **Post date:** [September 16, 2026, 9:29am UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948/12 "2026-09-16T09:29:15Z")
Hello 🙂 Thanks for the response. We are on SonarCloud. ---
**Author:** ![Farah](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/farah/32/60691_2.png) [@Farah](https://community.sonarsource.com/u/Farah)\ **Post date:** [September 16, 2026, 9:43am UTC](https://community.sonarsource.com/t/strange-oauth-problem/180948/13 "2026-09-16T09:43:50Z")
Great, we’ll tackle this subject soon and get back to you. Thank you!