SonarQube Cloudvf.sr

Claude Code

1. Run this in a terminal, in your project folder:

claude mcp add --transport http sonarqube-cloud https://api.sonarcloud.io/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

1. Replace the placeholder with your key before you run it, then check it with /mcp inside Claude Code.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

1. Custom connectors can't send this server's key header, so use the mcp-remote bridge. Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "sonarqube-cloud": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.sonarcloud.io/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}

1. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

{
  "mcpServers": {
    "sonarqube-cloud": {
      "url": "https://api.sonarcloud.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

VS Code

Add it to .vscode/mcp.json. VS Code asks for the key the first time and stores it securely:

{
  "servers": {
    "sonarqube-cloud": {
      "type": "http",
      "url": "https://api.sonarcloud.io/mcp",
      "headers": {
        "Authorization": "Bearer ${input:api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "api-key",
      "description": "API key",
      "password": true
    }
  ]
}

Devin Desktop

1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):

{
  "mcpServers": {
    "sonarqube-cloud": {
      "serverUrl": "https://api.sonarcloud.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add sonarqube-cloud --url https://api.sonarcloud.io/mcp --bearer-token-env-var SONARQUBE_CLOUD_API_KEY

Or edit ~/.codex/config.toml directly:

[mcp_servers.sonarqube-cloud]
url = "https://api.sonarcloud.io/mcp"
bearer_token_env_var = "SONARQUBE_CLOUD_API_KEY"

Set SONARQUBE_CLOUD_API_KEY to your key in the shell that runs Codex.

Gemini CLI

gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" sonarqube-cloud https://api.sonarcloud.io/mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

{
  "mcpServers": {
    "sonarqube-cloud": {
      "type": "http",
      "url": "https://api.sonarcloud.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://api.sonarcloud.io/mcp.

listing.em.badge

[![SonarQube Cloud on mcp.tc](https://mcp.tc/i/sonarqube-cloud/badge.svg)](https://mcp.tc/i/sonarqube-cloud)

<a href="https://mcp.tc/i/sonarqube-cloud"><img src="https://mcp.tc/i/sonarqube-cloud/badge.svg" alt="SonarQube Cloud on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

<script src="https://mcp.tc/w/sonarqube-cloud.js" async></script>

listing.em.widget_note

iframe

<iframe src="https://mcp.tc/embed/sonarqube-cloud" title="SonarQube Cloud on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/sonarqube-cloud.json

listing.em.fields