Sonarqube MCP
giuseppe-trisciuoglio/developer-kit
Provides SonarQube and SonarCloud integration patterns via the Model Context Protocol (MCP) server.
Find files with low test coverage and inspect uncovered lines in a SonarQube project (project key optional when MCP integration already defines the default project)
Install Sonar Coverage
$ npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SonarSource/sonarqube-agent-plugins sonar-coverage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SonarSource/sonarqube-agent-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sonar-coverage .claude/skills/sonar-coverage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sonar-coverage" agent skill from https://github.com/SonarSource/sonarqube-agent-plugins/tree/master/skills/sonar-coverage into .claude/skills/sonar-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sonar-coverage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SonarSource/sonarqube-agent-plugins/tree/master/skills/sonar-coverageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SonarSource/sonarqube-agent-plugins sonar-coverage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SonarSource/sonarqube-agent-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sonar-coverage .agents/skills/sonar-coverage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sonar-coverage" agent skill from https://github.com/SonarSource/sonarqube-agent-plugins/tree/master/skills/sonar-coverage into .agents/skills/sonar-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sonar-coverage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SonarSource/sonarqube-agent-plugins sonar-coverage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SonarSource/sonarqube-agent-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sonar-coverage .cursor/skills/sonar-coverage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sonar-coverage" agent skill from https://github.com/SonarSource/sonarqube-agent-plugins/tree/master/skills/sonar-coverage into .cursor/skills/sonar-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sonar-coverage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SonarSource/sonarqube-agent-plugins.git --path skills/sonar-coverage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SonarSource/sonarqube-agent-plugins sonar-coverage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SonarSource/sonarqube-agent-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sonar-coverage .gemini/skills/sonar-coverage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sonar-coverage" agent skill from https://github.com/SonarSource/sonarqube-agent-plugins/tree/master/skills/sonar-coverage into .gemini/skills/sonar-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sonar-coverage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SonarSource/sonarqube-agent-plugins sonar-coverageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SonarSource/sonarqube-agent-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sonar-coverage .github/skills/sonar-coverage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sonar-coverage" agent skill from https://github.com/SonarSource/sonarqube-agent-plugins/tree/master/skills/sonar-coverage into .github/skills/sonar-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sonar-coverage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SonarSource/sonarqube-agent-plugins sonar-coverage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SonarSource/sonarqube-agent-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sonar-coverage .opencode/skills/sonar-coverage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sonar-coverage" agent skill from https://github.com/SonarSource/sonarqube-agent-plugins/tree/master/skills/sonar-coverage into .opencode/skills/sonar-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sonar-coverage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sonar-coverage- GitHub stars
- 111
- Token cost
- ~2.1k tokens
- SKILL.md length
- 889 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Find files with low test coverage and inspect uncovered lines in a SonarQube project (project key optional when MCP integration already defines the default project)
- Works in 4 steps: Resolve the project key (only when needed) → Parse optional flags from the… → Run the appropriate flow → …
- Tasks that involve MCP servers
- SKILL.md covers Usage, Prerequisites and Instructions
- Calls docker and podman
What it does
Sonar Coverage is an agent skill from SonarSource/sonarqube-agent-plugins, published by the product's own GitHub organization. Find files with low test coverage and inspect uncovered lines in a SonarQube project (project key optional when MCP integration already defines the default project)
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering MCP servers and Test coverage. It works with Model Context Protocol and Docker. The repository describes itself as: SonarQube Plugin for AI Agents.
When your agent uses it
- Tasks that involve MCP servers
- Tasks that involve Test coverage
Example prompts
- “/sonar-coverage”
Requirements
- Docker
- Pre-approved tools (allowed-tools): Read, Grep, Bash(docker ps:*), Bash(podman ps:*), Bash(nerdctl ps:*), Bash(sonar:*)
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Resolve the project key (only when needed)
- Parse optional flags from the user-provided arguments
- Run the appropriate flow
- Next steps
What it can do on your machine
Read from SKILL.md and the folder at commit 6142e57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepBash(docker ps:*)Bash(podman ps:*)Bash(nerdctl ps:*)Bash(sonar:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
dockerpodman
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sonar Coverage loads about 2.1k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 889 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 889 words (~2,052 tokens).
“Identify files with insufficient test coverage and pinpoint the exact lines that need tests.”
- name
- sonar-coverage
- allowed-tools
- Read, Grep, Bash(docker ps:*), Bash(podman ps:*), Bash(nerdctl ps:*), Bash(sonar:*)
- argument-hint
- [project-key?] [--max n] [--file key] [--pr id]
Files
Just SKILL.md in skills/sonar-coverage of SonarSource/sonarqube-agent-plugins.
Open the folder on GitHubat commit 6142e57
Compare with similar skills
Sonar Coverage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sonar Coverage this skillSonarSource/sonarqube-agent-plugins | 111 | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Sonarqube MCPgiuseppe-trisciuoglio/developer-kit | 355 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Sentry Issue Fixergenlayerlabs/genlayer-studio | 180 | — | ~2k | Automated safety check: Pass | MIT | |
| Unraiddinglebear-ai/unraid | 135 | — | ~5.4k | Automated safety check: Notes | MIT | |
| Devsydevsy-org/devsy | 110 | — | ~1.7k | Automated safety check: Pass | MPL-2.0 | |
| Project Releaseswimmwatch/cloakbrowser-mcp | 161 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Sentry Issue Fixer
genlayerlabs/genlayer-studio
Fetch, analyze, fix Sentry issues, run tests, and create PRs
Unraid
dinglebear-ai/unraid
This skill should be used when the user mentions Unraid, asks to check server health, monitor array or disk status, list or restart Docker containers, start or stop VMs, read system logs, check…
Devsy
devsy-org/devsy
Operate Devsy workspaces and providers for end users. An agent skill from devsy-org/devsy.
Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
Pluggedin Stack Ops
VeriTeknik/pluggedin-app
A skill your agent uses when deploying, restarting, verifying or rolling back the containerised plugged.in production stack, when the site returns 404 or 5xx after a deploy or git operation, or when…
More from SonarSource/sonarqube-agent-plugins
All 8 skills in this repo- Official
Sonar Analyze
SonarSource/sonarqube-agent-plugins
Analyze a file for quality and security issues using SonarQube
- Official
Sonar Dependency Risks
SonarSource/sonarqube-agent-plugins
Search for software composition analysis (SCA) dependency risks in a SonarQube project (project key optional when MCP integration already defines the default project)
- Official
Sonar Duplication
SonarSource/sonarqube-agent-plugins
Find files with code duplications in a SonarQube project and inspect duplication blocks for a file (project key optional when MCP integration already defines the default project)
- Official
Sonar Fix Issue
SonarSource/sonarqube-agent-plugins
Fix a specific SonarQube issue in code by rule key and location
- Official
Sonar List Issues
SonarSource/sonarqube-agent-plugins
Search and filter SonarQube issues for a project, branch, or pull request via sonarqube-cli (-p is always required on the CLI; resolve the key from user arguments or sonar-project.properties)
- Official
Sonar List Projects
SonarSource/sonarqube-agent-plugins
List SonarQube projects accessible to the current user. An agent skill from SonarSource/sonarqube-agent-plugins.
Related
Works with
Categories
Questions about Sonar Coverage
What does Sonar Coverage do?
Find files with low test coverage and inspect uncovered lines in a SonarQube project (project key optional when MCP integration already defines the default project). Sonar Coverage is an agent skill from SonarSource/sonarqube-agent-plugins, published by the product's own GitHub organization.
When should I use Sonar Coverage?
Sonar Coverage fits situations like: tasks that involve MCP servers; tasks that involve Test coverage.
How do I install Sonar Coverage in Claude Code?
Run `npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a claude-code`. Or copy the skill folder (skills/sonar-coverage in SonarSource/sonarqube-agent-plugins) into .claude/skills/sonar-coverage in your project. Claude Code loads it when a task matches its description.
How do I install Sonar Coverage in Codex?
Run `npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a codex`. Or copy the skill folder (skills/sonar-coverage in SonarSource/sonarqube-agent-plugins) into .agents/skills/sonar-coverage in your project. Codex loads it when a task matches its description.
Can I use Sonar Coverage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SonarSource/sonarqube-agent-plugins --skill sonar-coverage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sonar-coverage, .gemini/skills/sonar-coverage, .github/skills/sonar-coverage and .opencode/skills/sonar-coverage in your project.
What does Sonar Coverage need to run?
Going by SKILL.md and its folder, Sonar Coverage needs the command-line tools its instructions call (docker and podman). Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Grep, Bash(docker ps:*), Bash(podman ps:*), Bash(nerdctl ps:*), Bash(sonar:*).
Does Sonar Coverage access the network?
SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Sonar Coverage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sonar Coverage use?
Sonar Coverage has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Sonar Coverage use?
About 2.1k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sonar Coverage?
Skills that share tags, products or a category with Sonar Coverage: Sonarqube MCP (giuseppe-trisciuoglio/developer-kit, 355 stars), Sentry Issue Fixer (genlayerlabs/genlayer-studio, 180 stars), Unraid (dinglebear-ai/unraid, 135 stars) and Devsy (devsy-org/devsy, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sonar Coverage?
SonarSource (a GitHub organization, an official publisher) maintains it in SonarSource/sonarqube-agent-plugins, which has 111 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: SonarSource/sonarqube-agent-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.