Search for:
Why this server?
Provides access to coding style guidelines and best practices, which can help address SonarQube findings related to code style.
Why this server?
Provides clj-kondo linting capabilities for Clojure/ClojureScript/EDN files, useful for environments that lack built-in linting. This helps fix findings related to linting issues in Clojure projects.
Why this server?
Allows LLMs to run Azure CLI commands which can be used to fix security issues found by SonarQube in Azure environments.
Why this server?
This server integrates with Sonar API to provide Claude with real-time web search capabilities for comprehensive research on code quality best practices.
Why this server?
Bridges Large Language Models with Language Server Protocol interfaces, allowing LLMs to access LSP's diagnostics and code actions for improved code suggestions.
Why this server?
AiDD MCP Server provides a secure interface for AI agents to perform file system operations and code analysis, enhancing AI-assisted development workflows across multiple programming languages.
Why this server?
Provides tools to read, search, and manipulate Git repositories, which could be useful for managing changes related to fixing SonarQube findings.
Why this server?
Provides code reviews with a sarcastic and cynical tone, helping identify issues in PRs and providing feedback on code quality, similar to SonarQube analysis.
Why this server?
Capable of interpreting golang code and judge it under the most strict ddd and clean architecture paradigms, which can help identify architectural issues that SonarQube might flag.
Why this server?
As LLMs are very good at generating Azure CLI commands, this server allows your LLM to list resources, update/create/delete them, fix errors (by looking at the logs), fix security issues...