No user-submitted related servers found.
Scored across 8 tools
The code_quality_* and jetbrains_* prefixes clearly separate the unified analysis layer from the PyCharm-specific backend. The three analyze scopes (files, git changes, project) are distinct, though code_quality_status and jetbrains_ide_status overlap somewhat in reporting backend health.
Most tools follow a consistent prefix + verb_noun pattern, e.g., code_quality_analyze_files and jetbrains_inspect_files. The status tools (code_quality_status, jetbrains_ide_status) deviate slightly by omitting a leading verb, but the pattern is otherwise predictable.
Eight tools is a reasonable size for a code quality server. The set feels slightly heavier than necessary because the jetbrains_inspect_* tools duplicate the analysis scope of the code_quality_analyze_* tools, but the redundancy is intentional for direct backend access.
The core workflow is well covered: check backend status, analyze files, analyze git changes, analyze the whole project, and clear cache. Minor gaps include no explicit Sonar-only analysis tool, no problem suppression or rule configuration, and the 200-file limit without a continuation mechanism.