SonarQube

Created By
dhanush-dev01a year ago
The SonarQube MCP (Model Context Protocol) Server is a custom-built AI-powered backend designed to integrate with SonarQube and enable intelligent, context-aware interactions between static code analysis and modern AI agents like GitHub Copilot, VS Code Agents, or any LLM-powered tool.
Overview

what is SonarQube MCP Server?

SonarQube MCP Server is an AI-powered backend designed to integrate with SonarQube, enabling intelligent interactions between static code analysis and modern AI agents like GitHub Copilot and VS Code Agents.

how to use SonarQube MCP Server?

To use the SonarQube MCP Server, set up your environment variables, install the required dependencies, and run the server using Python. You can also build and run it using Docker for easier deployment.

key features of SonarQube MCP Server?

  • Health Check: Monitor the status of your SonarQube server.
  • Token Validation: Validate SonarQube authentication tokens.
  • Project Issues: Fetch unresolved issues for specific projects.
  • Project Listing: List all accessible SonarQube projects.
  • Project Metrics: Retrieve key quality metrics for projects.

use cases of SonarQube MCP Server?

  1. Integrating AI tools with SonarQube for enhanced code analysis.
  2. Monitoring code quality in real-time during development.
  3. Automating issue tracking and reporting for software projects.

FAQ from SonarQube MCP Server?

  • Can I use SonarQube MCP Server with any version of SonarQube?

Yes, as long as the API endpoints are compatible.

  • Is there a graphical interface for SonarQube MCP Server?

No, it is designed to be used via API endpoints.

  • How do I handle errors when using the server?

The server includes comprehensive error handling and returns detailed error messages for diagnosis.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dhanush-dev01
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago