Report availability and status of both analysis backends: the JetBrains MCP Server (PyCharm inspections, default) and SonarQube for IDE (optional). Use this first to see which backends are configured and ready.

Analyze 1 to 200 absolute file paths with the default backend strategy (backend_mode=auto: JetBrains first, Sonar auto-added if installed). Returns unified findings after deterministic cross-backend deduplication. Errors-only filtering and deduplication mode are configurable.

Collect changed files in the git repository under project_root (staged, unstaged, untracked; relative to base_ref) and analyze them with the unified backend strategy. Deleted files are excluded. Same deduplication and backend_mode options as code_quality_analyze_files.

Scan all files in the git repository under project_root (default: all .py files, tracked + untracked, .gitignore-respected) and analyze them with the unified backend strategy. Use this when you want the whole repo rather than just git changes. Pass extensions to scan other file types. Subject to the same 200-file limit and deduplication options as code_quality_analyze_files.

Clear in-memory caches for all backends (Sonar port discovery, JetBrains session). Pass project_root to clear only one Sonar project's port mapping.

Probe the locally-configured JetBrains MCP Server (PyCharm) and report whether it is configured, reachable, project-ready, and whether the required tool (get_file_problems) is exposed. get_project_status is reported as optional (absent on PyCharm 2026.1+). Use this for diagnostics.

Inspect 1 to 200 absolute file paths with PyCharm's built-in JetBrains inspections via the local JetBrains MCP Server. Reuses one MCP session for all files; a single file failure does not abort the others. Returns inspection problems (1-based ranges).

Collect changed files in the git repository under project_root (staged, unstaged, untracked; relative to base_ref) and inspect them with JetBrains inspections. Deleted files are excluded.