sonarqube-mcp-server and sonarlint-mcp-server
These are complementary tools that serve different scopes: SonarQube is a centralized, server-based platform for organization-wide code quality management, while SonarLint is a lightweight, client-side linter that provides real-time feedback during development and can integrate with SonarQube for consistency.
About sonarqube-mcp-server
SonarSource/sonarqube-mcp-server
SonarQube MCP Server
Implements an MCP server that connects AI agents to SonarQube for real-time code quality analysis and security scanning, supporting both Cloud and Server deployments. Enables inline code snippet analysis within agent contexts without requiring full repository integration. Deploys as a containerized service with stdio transport, integrating with Claude, Cursor, Gemini, and other MCP-compatible AI platforms through environment-based authentication.
About sonarlint-mcp-server
nielspeter/sonarlint-mcp-server
A Model Context Protocol (MCP) server that brings enterprise-grade code analysis to Claude Desktop and other MCP clients using SonarLint's standalone SLOOP backend.
Exposes standalone SLOOP backend analysis through stdio transport with in-memory result caching for multi-turn conversations, enabling Claude to perform real-time bug detection, security scanning, and automated fixes across JavaScript, TypeScript, and Python without requiring an IDE or SonarQube server. Implements bi-directional JSON-RPC with critical scope lifecycle management (pre-registering files, awaiting readiness signals) to prevent analysis hangs on large projects.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work