✓ Copied to clipboard!

SonarQube MCP Server Configuration Generator

Something not working? Reach out on the Sonar Community forum.

1 Target Client

2 SonarQube Server & Auth

🔒 Security recommendation — avoid hardcoding your token

Pasting your token here embeds it in plain text inside your config file, which can end up in version control or be read by other processes. Consider these safer alternatives instead:

  • Environment variable substitution — most clients support referencing a shell variable directly in the config, e.g. ${SONARQUBE_TOKEN} or $env:SONARQUBE_TOKEN (PowerShell). Leave the field empty here and set the placeholder yourself.
  • Secrets manager — inject the token at runtime via your OS keychain, HashiCorp Vault, AWS Secrets Manager, or similar, and expose it as an env var.
  • CI/CD secrets — if you are generating a config for a pipeline, use your CI platform's native secret injection (GitHub Actions secrets, GitLab CI variables, etc.).
  • Short-lived tokens — generate a token with a short expiry and rotate it regularly to limit exposure.
If provided, it will be injected into the config. Keep this secret! Leave empty to keep <YOUR_TOKEN> placeholder. How to get a token

3 Connection Mode

4 Toolsets & Advanced

Generated Configuration Not Selected
Please select a Target Client (Step 1) to build the configuration.

⚠️ Do not share this generated text with others if it contains your private SonarQube token.