Skip to main content

sonar-list-projects

List SonarQube projects accessible to the current user via the SonarQube MCP Server

Zur Installation springen

Quellinformationen

Repository
SonarSource/sonarqube-gh-agent-apps-plugin
Letzte Quellaktivität
3. Juni 2026 um 13:40
Erkannte Sprache von SKILL.md
Englisch
Sterne
1
Forks
3

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
sonar-list-projects
description
List SonarQube projects accessible to the current user via the SonarQube MCP Server
argument-hint
[search-query] [--page n] [--page-size n]
# SonarQube — List Projects List SonarQube projects accessible to the authenticated user. Useful for discovering project keys before running other skills. ## Usage ``` sonar-list-projects # list accessible projects sonar-list-projects my-project # search by name (partial) or key (exact) sonar-list-projects --page 2 # next page of results sonar-list-projects --page-size 100 # limit page size ``` ## Prerequisites This skill requires the SonarQube MCP Server to be configured and the tool `mcp__sonarqube__search_my_sonarqube_projects` to be available in your session. If a tool fails due to authentication problems, ask the user to ensure they have given their consent for automatic token exchange through SonarQube Cloud > My Account > Access Tokens > Agent Apps. Otherwise surface the tool error verbatim and stop. ## Instructions ### Step 1: Parse arguments - The first non-flag argument (if present) is the search term and maps to `q`. - `--page <n>` maps to `page` (string, defaults to `1`). - `--page-size <n>` maps to `pageSize` (integer 1–500, defaults to 500). ### Step 2: Validate arguments | Argument | Allowed pattern / values | | ------------- | ------------------------ | | search term | `^[a-zA-Z0-9_\-\. ]+$` | | `--page` | positive integer | | `--page-size` | integer 1–500 | If a value fails validation, stop and tell the user what was rejected — do not run the call. ### Step 3: Call `mcp__sonarqube__search_my_sonarqube_projects` ```json { "q": "<search-term>", "page": "<n>", "pageSize": <n> } ``` Omit any field the user did not provide. ### Step 4: Format the results **If projects are found**: ```markdown ## SonarQube Projects Found **8 project(s)**: | Project key | Name | | ----------------- | --------------- | | my-org_backend | Backend Service | | my-org_frontend | Frontend App | | my-org_shared-lib | Shared Library | ``` **If no projects are found**: ```markdown ## SonarQube Projects No projects found. ``` **If more results are likely** (response is full to `pageSize`): *"Showing page N. Use `--page <n+1>` to see more, or pass a search term to narrow results."* ### Step 5: Next steps - To list issues: *"Invoke the sonar-list-issues skill with the project key, or rely on the MCP integration default."* - To check the quality gate: *"Invoke the sonar-quality-gate skill — add a project key only if you are not using the MCP integration default."*
Auf GitHub ansehen