"PyCharm" matching MCP tools:

• code_quality_statusA

  pycharm-code-quality-mcpA

  Check availability of configured code analysis backends: JetBrains PyCharm inspections and SonarQube for IDE. Run first to verify which are ready.

  MIT

• jetbrains_ide_statusA

  pycharm-code-quality-mcpA

  Probe the locally-configured JetBrains IDE (PyCharm) and report whether it is configured, reachable, project-ready, and exposes the required get_file_problems tool.

  MIT

• code_quality_clear_cacheA

  pycharm-code-quality-mcpA

  Clears in-memory caches for code quality backends (Sonar port discovery, JetBrains session). Optionally target a specific project root to clear only its port mapping.

  MIT

• code_quality_analyze_filesA

  pycharm-code-quality-mcpA

  Analyze code quality of 1 to 200 files using JetBrains and optional SonarQube backends, with unified deduplicated results and configurable filtering.

  MIT

• jetbrains_inspect_filesA

  pycharm-code-quality-mcpA

  Inspect 1 to 200 absolute file paths using PyCharm's built-in code inspections to detect errors and code quality issues, returning problems with 1-based ranges.

  MIT

• code_quality_analyze_git_changesA

  pycharm-code-quality-mcpA

  Analyze code quality of git changes by collecting changed files (staged, unstaged, untracked) and running unified inspections. Excludes deleted files.

  MIT

• jetbrains_inspect_git_changesA

  pycharm-code-quality-mcpA

  Inspect code quality of git changes using JetBrains inspections. Analyzes staged, unstaged, and untracked files relative to a base ref.

  MIT

• code_quality_analyze_projectA

  pycharm-code-quality-mcpA

  Scan and analyze all files in a git repository using unified code quality inspections, supporting custom file extensions and deduplication. Use for full project analysis.

  MIT