JetBrains Code Inspections FAQs

Question 1

What is JetBrains Code Inspections?

Accepted Answer

It's a Model Context Protocol (MCP) server designed to automate code inspections using your existing JetBrains IDEs. It provides consistent static analysis across various projects with features like automatic IDE detection and a unified inspection profile.

Question 2

Which JetBrains IDEs are supported by this tool?

Accepted Answer

The tool supports a wide range of JetBrains IDEs including IntelliJ IDEA, WebStorm, PyCharm, PhpStorm, GoLand, Rider, CLion, RubyMine, DataGrip, DataSpell, and AppCode. It automatically detects and uses the first available IDE.

Question 3

Can I run inspections even if my JetBrains IDE is already open?

Accepted Answer

Yes, a significant feature of this tool is its ability to run inspections with isolated configurations. This means it operates independently, allowing inspections to proceed without interfering with your active IDE session.

Question 4

What output formats are available for the code inspection diagnostics?

Accepted Answer

The diagnostics are primarily output in Markdown format, which is optimized for Large Language Models (LLMs). An optional JSON format is also available for programmatic parsing and integration.

Question 5

How does the tool handle inspection profiles and configurations?

Accepted Answer

It uses a unified inspection profile that supports all languages and file types by default. You can customize inspections by excluding specific codes via environment variables like `EXCLUDE_INSPECTIONS`, or by forcing a specific profile path.

JetBrains Code Inspections

JetBrains Code Inspections

Key Features

Use Cases

Key Features

Use Cases