How to get JetBrains IDE 'Problems' view inspection results via mcp-jetbrains?
With mcp-jetbrains in early 2025, an AI agent like Claude Code needs the inspection results the IDE shows in the Problems view (errors, warnings, SonarLint results). Listing the MCP tools via
curl http://127.0.0.1:63342/api/mcp/list_toolsshows many tools, but nothing that returns those problems. Does mcp-jetbrains have a tool for this, and can it target a specific file?Originally asked on GitHub: https://github.com/JetBrains/mcp-jetbrains/issues/31
3 answers
Fixed: a maintainer added the requested tools and the issue is closed as completed. The thread does not state the closing date or a specific plugin version, but the tools were confirmed to exist in the latest version at the time (April 2025).
Per the maintainer's comment, the four added MCP tools are:
get_project_problems— exposes the project's Problems view entries.get_current_file_errors— errors for the file currently open in the editor.reformat_current_file— reformats the open file.reformat_file— reformats a given file.
To see which tools your installed version exposes, run:
bashcurl http://127.0.0.1:63342/api/mcp/list_toolsThere is no
get_file_errorstool for an arbitrary file. One commenter asked for one because they prefer editing files outside the IDE (terminal, another editor), tried implementing it themselves, and reported that waiting for the IDE's analysis to complete was the blocker. General advice: if you need inspection results for a file that is not open,get_project_problemsis the tool to try, filtering by file path yourself.The maintainer did not add definition/find-usages tools, saying they are probably not needed since an LLM can find the source using the text most of the time. One commenter also asked whether
get_current_file_errorscorresponds to the error indicator in the top-right corner of the file tab; that was not confirmed in the thread.Did this work for you?What a GitHub user tried on GitHub (Didn't work)
The reporter listed the MCP server tools with
curl http://127.0.0.1:63342/api/mcp/list_toolsand confirmed there was no tool exposing the IDE Problems view entries.Source: https://github.com/JetBrains/mcp-jetbrains/issues/31 (opens external site)
Did this work for you?What @Lewik tried on GitHub (Didn't work)
A commenter tried to implement a
get_file_errorstool themselves but couldn't figure out how to wait for IDEA's analysis to complete, so no working patch was produced.Source: https://github.com/JetBrains/mcp-jetbrains/issues/31#issuecomment-2798097287 (opens external site)
Did this work for you?
Related questions
- JetBrains MCP proxy: connected but no available tools in Claude
- mcp-jetbrains returns 429 rate limit errors with empty logs — cause and fix?
- Claude Desktop doesn't show JetBrains MCP tools: how to fix?
- How to filter which JetBrains MCP tools are exposed to Claude Code?
- JetBrains MCP in Claude Desktop: 'No working IDE endpoint available' on tools/list