analyze_callsLABSCO SUMMARY
The IDE's own analysis, handed to an outside agent.
The draw is precision: call hierarchy and inspections come from the IDE's index, so an agent asks one question where it would otherwise grep four times. The setting to look at before you enable it is brave mode, which lets connected clients run terminal commands and run configurations without asking you each time.
What it is
The MCP server built into JetBrains IDEs from version 2025.2. External clients such as Claude Code, Codex or VS Code connect to the running IDE and use what it knows about your project: the call hierarchy, the inspections, the debugger, the VCS state.
What you get
- Call hierarchy through analyze_calls — who calls a symbol and what it calls, from IDE data rather than a text search
- Inspections and compile errors via get_file_problems, lint_files and build_project
- Refactoring the IDE performs rather than text replacement: rename_refactoring
- A debugger an agent can drive — xdebug_set_breakpoint, xdebug_evaluate_expression, xdebug_get_stack
- Database work over the IDE's own connections: introspect_schema, execute_sql_query, preview_table_data
- Symbol, text, regex and file search, plus execute_terminal_command and git_status
- Per-tool switches under Settings | Tools | MCP Server | Exposed Tools, and a router-only mode that keeps unused tool descriptions out of the client's context
Requirements
A JetBrains IDE at 2025.2 or newer with the bundled MCP Server plugin left enabled, and the server switched on under Settings | Tools | MCP Server. Detected clients configure themselves from that screen; anything else takes a copied SSE, stdio or HTTP stream config.
Setup effort
Follow the published steps
USE CASES
01
Working out what breaks if you change a method
Ask for the callers of the symbol and get the IDE's call hierarchy, which is the same answer the IDE would give you — not a guess from matching text.
02
Checking that an edit actually compiles
Build the project or just the touched files, and read back the errors and warnings before moving on.
03
Following a bug into a running program
Set a breakpoint, start the run configuration, then read the stack and evaluate expressions in the frame where it stopped.
04
Answering a question that needs the database, not the code
Use a connection already configured in the IDE: read the schema, preview a table, then run the query.
05
Renaming something without breaking references
The IDE performs the rename across the project, so references and imports move with it.
58 tools
Listed in project docs. Your client may show a different list.
build_projectget_file_problemsget_project_dependenciesget_project_moduleslint_filesget_symbol_infocancel_sql_querycreate_database_connectionedit_database_connectionexecute_sql_queryfetch_query_resultget_database_object_descriptionintrospect_schemalist_database_connectionslist_database_schemaslist_recent_sql_querieslist_schema_object_kindslist_schema_objectspreview_table_datatest_database_connectionxdebug_control_sessionxdebug_evaluate_expressionxdebug_get_debugger_statusxdebug_get_frame_valuesxdebug_get_stackxdebug_get_threadsxdebug_get_value_by_pathxdebug_list_breakpointsxdebug_remove_breakpointxdebug_run_to_linexdebug_set_breakpointxdebug_set_variablexdebug_start_debugger_sessionexecute_run_configurationget_run_configurationscreate_new_fileget_all_open_file_pathslist_directory_treeopen_file_in_editorreformat_filevalidate_inspection_ktsgenerate_inspection_kts_apigenerate_inspection_kts_examplesgenerate_psi_treerun_inspection_ktsapply_patchread_filerename_refactoringsearch_filesearch_regexsearch_symbolsearch_textskill_searchexecute_terminal_commandexecute_toolget_repositoriesgit_statusBEFORE YOU INSTALL
What to know first
Tools you get
58 tools named in the project's documentation.
Requires
- IntelliJ IDEA or another IntelliJ-based JetBrains IDE, version 2025.2 or newer
- The bundled MCP Server plugin left enabled
INSTALLATION
Connect your client
Server setup
Use IntelliJ IDEA or another IntelliJ-based JetBrains IDE at version 2025.2 or newer — the MCP server is built in, through the MCP Server plugin that is bundled and enabled by default.
Go to Settings | Tools | MCP Server, select the Enable MCP Server checkbox, click Enable in the dialog, then click Apply.
For Junie, VS Code, Claude Code, Codex, Air or GitHub Copilot CLI: in the Clients Auto-Configuration section of the same screen, click Auto-Configure for the client, then restart the client.
For any other client: in the Manual Client Configuration section, click Copy SSE Config, Copy Stdio Config or Copy HTTP Stream Config, paste it into the client's configuration file, then restart the client.
Keep the IDE open with your project while you use it — the tools run inside the IDE.
