We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

SonarQube, verified

MCP server by SonarSource · Verified

Check code quality and security issues, quality gates and code snippets with SonarQube Server or SonarQube Cloud from your AI assistant.

Runs locally (Runs on your machine: its page has the install command)Runs with dockerNeeds an API key

Install SonarQube

Runs on your machine. Your client starts it with this command:

docker run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG sonarsource/sonarqube-mcp

Needs Docker on your computer. The setup steps below show where the command goes in each client.

  • SONARQUBE_TOKEN secret Your SonarQube USER token
  • SONARQUBE_ORG secret optional Your SonarQube Cloud organization key (if using SonarQube Cloud)
  • SONARQUBE_URL secret optional Your SonarQube Server URL (if using SonarQube Server)

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/sonarqube

About

Connects an AI assistant to SonarQube Server or SonarQube Cloud for code quality and security data. It can read issues and quality gate results from your projects, and it can analyze code snippets directly in the agent context.

It runs locally as a Docker container (sonarsource/sonarqube-mcp) over stdio. A SonarQube user token is required in SONARQUBE_TOKEN. Set SONARQUBE_ORG for SonarQube Cloud, or SONARQUBE_URL for SonarQube Server. SonarQube Cloud also offers a hosted endpoint with a smaller, fixed set of tools.

What you can do

  • Look up code quality and security issues in SonarQube projects
  • Check quality gate status
  • Analyze code snippets inside the agent context
  • Work with SonarQube Server or SonarQube Cloud
  • Run as a local Docker container

Tools

SonarQube lists its tools only to clients with a key, so we can’t show them here.

Example prompts

  • List the open security issues in my SonarQube project

  • Does my project pass its SonarQube quality gate?

  • Analyze this code snippet for quality and security problems

  • Show the highest severity issues on the main branch

Set up

Every client starts SonarQube on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio sonarqube --env "SONARQUBE_TOKEN=<YOUR_SONARQUBE_TOKEN>" --env "SONARQUBE_ORG=<YOUR_SONARQUBE_ORG>" --env "SONARQUBE_URL=<YOUR_SONARQUBE_URL>" -- docker run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG sonarsource/sonarqube-mcp
  1. Start Claude Code and type /mcp. sonarqube should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "sonarqube": {
      "command": "docker",
      "args": [
        "run",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "-e",
        "SONARQUBE_URL",
        "--init",
        "--pull=always",
        "-i",
        "--rm",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "sonarsource/sonarqube-mcp"
      ],
      "env": {
        "SONARQUBE_TOKEN": "<YOUR_SONARQUBE_TOKEN>",
        "SONARQUBE_ORG": "<YOUR_SONARQUBE_ORG>",
        "SONARQUBE_URL": "<YOUR_SONARQUBE_URL>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Docker on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

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

mcp.json
{
  "mcpServers": {
    "sonarqube": {
      "command": "docker",
      "args": [
        "run",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "-e",
        "SONARQUBE_URL",
        "--init",
        "--pull=always",
        "-i",
        "--rm",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "sonarsource/sonarqube-mcp"
      ],
      "env": {
        "SONARQUBE_TOKEN": "<YOUR_SONARQUBE_TOKEN>",
        "SONARQUBE_ORG": "<YOUR_SONARQUBE_ORG>",
        "SONARQUBE_URL": "<YOUR_SONARQUBE_URL>"
      }
    }
  }
}

Needs Docker on your computer. Replace the placeholders with your own values.

VS Code

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

.vscode/mcp.json
{
  "servers": {
    "sonarqube": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "-e",
        "SONARQUBE_URL",
        "--init",
        "--pull=always",
        "-i",
        "--rm",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "sonarsource/sonarqube-mcp"
      ],
      "env": {
        "SONARQUBE_TOKEN": "${input:sonarqube-token}",
        "SONARQUBE_ORG": "${input:sonarqube-org}",
        "SONARQUBE_URL": "${input:sonarqube-url}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "sonarqube-token",
      "description": "SONARQUBE_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "sonarqube-org",
      "description": "SONARQUBE_ORG",
      "password": true
    },
    {
      "type": "promptString",
      "id": "sonarqube-url",
      "description": "SONARQUBE_URL",
      "password": true
    }
  ]
}

Needs Docker on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "sonarqube": {
      "command": "docker",
      "args": [
        "run",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "-e",
        "SONARQUBE_URL",
        "--init",
        "--pull=always",
        "-i",
        "--rm",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "sonarsource/sonarqube-mcp"
      ],
      "env": {
        "SONARQUBE_TOKEN": "<YOUR_SONARQUBE_TOKEN>",
        "SONARQUBE_ORG": "<YOUR_SONARQUBE_ORG>",
        "SONARQUBE_URL": "<YOUR_SONARQUBE_URL>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add sonarqube --env "SONARQUBE_TOKEN=<YOUR_SONARQUBE_TOKEN>" --env "SONARQUBE_ORG=<YOUR_SONARQUBE_ORG>" --env "SONARQUBE_URL=<YOUR_SONARQUBE_URL>" -- docker run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG sonarsource/sonarqube-mcp

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

config.toml
[mcp_servers.sonarqube]
command = "docker"
args = ["run", "--init", "--pull=always", "-i", "--rm", "-e", "SONARQUBE_TOKEN", "-e", "SONARQUBE_ORG", "sonarsource/sonarqube-mcp"]
env = { SONARQUBE_TOKEN = "<YOUR_SONARQUBE_TOKEN>", SONARQUBE_ORG = "<YOUR_SONARQUBE_ORG>", SONARQUBE_URL = "<YOUR_SONARQUBE_URL>" }

Needs Docker on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "SONARQUBE_TOKEN=<YOUR_SONARQUBE_TOKEN>" -e "SONARQUBE_ORG=<YOUR_SONARQUBE_ORG>" -e "SONARQUBE_URL=<YOUR_SONARQUBE_URL>" sonarqube docker -- run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG sonarsource/sonarqube-mcp

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

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "sonarqube": {
      "command": "docker",
      "args": [
        "run",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "-e",
        "SONARQUBE_URL",
        "--init",
        "--pull=always",
        "-i",
        "--rm",
        "-e",
        "SONARQUBE_TOKEN",
        "-e",
        "SONARQUBE_ORG",
        "sonarsource/sonarqube-mcp"
      ],
      "env": {
        "SONARQUBE_TOKEN": "<YOUR_SONARQUBE_TOKEN>",
        "SONARQUBE_ORG": "<YOUR_SONARQUBE_ORG>",
        "SONARQUBE_URL": "<YOUR_SONARQUBE_URL>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Docker on your computer. Replace the placeholders with your own values.

Embed

Show SonarQube in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![SonarQube on mcp.tc](https://mcp.tc/i/sonarqube/badge.svg)](https://mcp.tc/i/sonarqube)
HTML
<a href="https://mcp.tc/i/sonarqube"><img src="https://mcp.tc/i/sonarqube/badge.svg" alt="SonarQube on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

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

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

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

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

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

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the SonarQube card to your site.

Markdown
Add the mcp.tc card for SonarQube, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

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

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="sonarqube"><a href="https://mcp.tc/i/sonarqube">SonarQube on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![SonarQube on mcp.tc](https://mcp.tc/i/sonarqube/badge.svg)](https://mcp.tc/i/sonarqube)
```

Reference: https://mcp.tc/embed

Change history

It runs on your computer and has no package we can follow. Edits by its owner show up here.

Follow SonarQube and we’ll email you when something changes.

Nothing recorded yet. Edits by the server’s owner will show up here.

FAQ

Can I paste mcp.tc/i/sonarqube into my MCP client?

No. SonarQube runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is docker run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG sonarsource/sonarqube-mcp.

Does SonarQube need an API key?

Yes. It reads SONARQUBE_TOKEN, SONARQUBE_ORG and SONARQUBE_URL from its environment, and SONARQUBE_TOKEN, SONARQUBE_ORG and SONARQUBE_URL are secrets. Put the values in your client’s config on your own machine, never in a shared file.

Is SonarQube a remote or a local server?

Local. Your client starts it as a process on your computer with docker run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG sonarsource/sonarqube-mcp, which needs Docker.

What can SonarQube do?

You can look up code quality and security issues in SonarQube projects, check quality gate status and analyze code snippets inside the agent context.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to SonarQube?

Partly. SonarQube runs on your computer and has no package we can follow, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read SonarQube’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with SonarSource. This page was built from SonarQube’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.