sonarlint-mcp
Related Servers
Alternatives to sonarlint-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for interacting with SonarQube code quality platform.333 PyPI1MIT
- FlicenseNot gradedqualityBmaintenanceExposes LSP features (definition, hover, references, etc.) over MCP, spawning an isolated language server process per project.-
- FlicenseNot gradedqualityDmaintenanceEnables access to SonarQube code quality analysis through MCP, including issue searching, metrics retrieval, and quality gate status.-
- FlicenseNot gradedqualityBmaintenanceGives AI coding agents a shared local SonarQube instance plus a SonarQube MCP endpoint per machine, so multiple clients can run scans, wait on quality gates, and read metrics and issues for the auto-detected project in a workspace. Tools also accept an optional server argument to query configured remote SonarQube servers (such as a company CI server) alongside the local one.-
- AlicenseNot gradedqualityAmaintenanceProvides comprehensive code quality analysis and automated fixing, available as a CLI and MCP server (currently in early beta with MCP part untested).1MIT
- AlicenseNot gradedqualityDmaintenanceExposes Language Server Protocol (LSP) tools such as diagnostics, goto definition, find references, symbols, and rename as a stdio MCP server.8MIT
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: scanning a file, scanning a folder, scanning the project, listing rules, getting a rule, and checking status. The main overlap is between sonarlint_scan_folder and sonarlint_scan_project, since a project scan is essentially a folder scan from the workspace root; the descriptions clarify this, but an agent may still hesitate between them.
All tools share the sonarlint_ prefix and mostly follow a verb_noun pattern: scan_folder, scan_project, scan_file, get_rule, list_rules. The only minor deviation is sonarlint_status, which uses a noun-only form rather than a verb, but it is still readable and consistent with the overall prefix.
Six tools is well-scoped for a SonarLint analysis server. Each tool covers a distinct operation needed for scanning code and inspecting rules/status, with no obvious filler.
The surface covers the core lifecycle: scan individual files, folders, and the whole project, plus inspect active rules, get rule details, and check engine status. Minor gaps exist around configuring rule activation/exclusions or retrieving richer issue metadata/fixes, but agents can work around these for basic analysis workflows.