"Sonar" matching MCP servers:

A Model Context Protocol (MCP) server for interacting with SonarQube code quality platform.

A local MCP server that provides Sonar-grade static analysis (bugs, vulnerabilities, code smells) for TypeScript/JS and C# repositories, with CLI and dashboard support.

Enables access to SonarQube code quality analysis through MCP, including issue searching, metrics retrieval, and quality gate status.

Enables real-time code analysis for JavaScript, TypeScript, and Python through Claude Desktop and other MCP clients, detecting bugs, code smells, and security vulnerabilities with automated quick fixes.

Enables Cursor AI to query SonarQube for pull request metrics, issues, file issues, and duplication reports directly, without manual data export.

Read-only MCP server that exposes SonarQube Web API tools for issue retrieval, quality gate status, and source context, enabling coding agents to fix code issues.

A server that enables fetching and filtering SonarCloud issues related to pull requests, making it easier to identify and fix code quality problems.

Exposes Panaya REST APIs as MCP tools for managing entities like projects, requirements, tests, defects, releases, cycles, and business processes. Enables Claude or any MCP client to perform CRUD operations on Panaya data via natural language.

Enables seamless integration with SonarQube Server or Cloud for code quality and security analysis. Supports querying project metrics, issues, and analyzing code snippets directly within the agent context.

Gives 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.