fetch_sonarcloud_issuesLABSCO SUMMARY
One tool, aimed at the review loop.
The interesting detail is the special assignee value SonarCloud resolves to the token owner, so a saved prompt can say "fetch my open issues on this PR, fix them, push" and work for whoever runs it. The README suggests parking exactly that prompt as a shortcut. The scope is narrow on purpose — this is not a SonarCloud browser, it is the piece that closes the loop between a scan result and a commit.
What it is
A focused MCP server for one workflow: fetching SonarCloud issues for a pull request so an AI client can act on them. It returns formatted issue data with severity, type and location rather than raw API payloads.
What you get
- SonarCloud issues scoped to one pull request, filterable by organization, project and PR number, with severity, type and location on each —
fetch_sonarcloud_issues - Status filtering, so a request can be narrowed to OPEN or ACCEPTED issues
- Assignee filtering that understands SonarCloud's special value for the token owner, which is what makes "fix the ones assigned to me" work
Requirements
A SonarCloud API token as SONARCLOUD_TOKEN — required. SONARCLOUD_ORGANISATION and SONARCLOUD_PROJECT_KEY are optional and can be passed per call instead. Two install paths: build the Docker image with npm run docker:build and run it with docker run -i --rm, or run npm ci then npm run build and point the client at dist/index.js. The package is sonarcloud-mcp (1.0.0 in package.json).
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Clearing your own SonarCloud findings on a PR
Fetch open and accepted issues assigned to the token owner for that PR, then work through them and push the fixes.
02
Seeing what a scan flagged before review
Pull the issues for the PR number with severity and location, so the discussion starts from the actual findings.
03
Working across more than one project
Pass the organization and project key per call instead of fixing them in the environment.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- docker on PATH
- SONARCLOUD_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Build the image from the repository, then point your client at it.
Server setup
TERMINAL
git clone https://github.com/dozzman/sonarcloud-mcp
cd sonarcloud-mcp
docker build -t sonarcloud-mcp .MCP Clients
Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"sonarcloud": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SONARCLOUD_TOKEN",
"-e",
"SONARCLOUD_ORGANISATION",
"-e",
"SONARCLOUD_PROJECT_KEY",
"sonarcloud-mcp"
],
"env": {
"SONARCLOUD_TOKEN": "<YOUR_SONARCLOUD_TOKEN>",
"SONARCLOUD_ORGANISATION": "<YOUR_SONARCLOUD_ORGANISATION>",
"SONARCLOUD_PROJECT_KEY": "<YOUR_SONARCLOUD_PROJECT_KEY>"
}
}
}
}
