# Jetbrains Skill

> Use the JetBrains IDE MCP Server (IntelliJ IDEA 2025.2+) to let an external client drive IDE-backed actions: run Run Configurations, execute commands in the IDE terminal, read/create/edit project files, search via IDE indexes (text/regex), retrieve code inspections for a file, fetch symbol info, perform rename refactoring, list modules/dependencies/repos, open files in the editor, and reformat code. Use when you want IDE-grade indexing/refactoring/inspection instead of raw shell scripting.

- Skill: `est7/jetbrains-skill` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add est7/jetbrains-skill`
- Raw SKILL.md: https://api.skillmd.com/api/skills/est7/jetbrains-skill/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: est7 (https://skillmd.com/u/est7)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/est7/jetbrains-skill

---


# JetBrains Skill

## Quick start

Goal: use JetBrains IDE features (index, inspections, refactoring, run configurations, integrated terminal) as tools for an external client, while keeping changes auditable and safe.

notes + tool list (condensed): `skills/jetbrains-skill/references/jetbrains-skill.md`.

## Connection & modes

### Client setup (done in the IDE)
- Settings → Tools → MCP Server
- Enable MCP Server
- Use “Auto-configure” for supported clients (updates their JSON config), or copy SSE / Stdio config for manual setup
- Restart the external client to apply changes

### Brave Mode (no confirmations)
The IDE can allow running shell commands / run configurations without per-action confirmation (“Brave mode”).
This increases automation power but also increases risk. Require explicit user confirmation before enabling/disabling it.

## Workflow decision tree

1) Do I need IDE-grade analysis/refactoring?
- File diagnostics: `get_file_problems`
- Symbol semantics / docs: `get_symbol_info`
- Safe rename across project: `rename_refactoring` (prefer over plain text replace)
- Indexed search: `search_in_files_by_text` / `search_in_files_by_regex`
- Find files: `find_files_by_name_keyword` (fast, name-only) or `find_files_by_glob` (path glob)

2) Do I just need file operations in the project?
- Read file text: `get_file_text_by_path`
- Create file: `create_new_file`
- Targeted replace: `replace_text_in_file` (auto-saves)
- Open in editor: `open_file_in_editor`
- Reformat: `reformat_file`

3) Do I need to run something?
- List run configs: `get_run_configurations`
- Run a config (wait for completion): `execute_run_configuration`
- Run a terminal command in IDE: `execute_terminal_command` (may require confirmation; output is capped)

## When NOT to use JetBrains MCP

- If JetBrains IDE is not open with the target project, or the MCP plugin is not running.
- For bulk text search/replace or simple edits: prefer CLI tools like `rg` and direct edits.
- For IDE-irrelevant tasks (docs updates, shell scripts, config cleanup): prefer the repo/CLI workflow.

## Constraints (avoid common mistakes)

- Always pass `projectPath` when known to avoid ambiguity.
- Many tools require paths relative to the project root and only operate on project files.
- Line/column positions are 1-based for location-based tools.
- Prefer controlling output with `maxLinesCount` + `truncateMode`; do not rely on defaults for large outputs.
- Terminal commands and running configurations are high-risk; require explicit confirmation for any potentially destructive command. Brave Mode removes guardrails.

### Safety & confirmation rules

**Requires user confirmation** (destructive or hard-to-revert impact):
- Batch apply Quick Fixes / auto-fixes
- Modify Run Configuration / Gradle / build settings
- Enabling/disabling Brave Mode
- `execute_terminal_command` (any potentially destructive command; ask if unsure)

**No confirmation needed** (read-only operations):
- Open file in editor, jump to definition
- List usages, view symbol info
- View Inspection report (without auto-fix)
- Search files (text/regex/name/glob)
- List modules, dependencies, repositories, run configurations

## Fallback when unavailable

When JetBrains MCP is unavailable (IDE not open / plugin disabled / endpoint unreachable):
- Code understanding: prefer `codebase-retrieval` (semantic) + `rg` (exact).
- Refactoring: use small, safe diffs; add tests/build verification as needed.
- Running: use repo-native commands (Gradle, pnpm/npm, pytest, etc.), not IDE Run Configurations.

## Recommended high-value patterns

### Debug via inspections first
1) `get_file_problems` to find errors/warnings → 2) `get_symbol_info` to understand the code → 3) `rename_refactoring` for renames → 4) `replace_text_in_file` only for truly textual changes.

### Use indexed search for scale
Prefer `search_in_files_by_text` / `search_in_files_by_regex` since it uses IDE search/indexing and highlights matches with `||`.

### Running and output control
Use `execute_run_configuration` with a sane `timeout` (ms). For terminal commands use `execute_terminal_command`, but remember output caps; for huge output, redirect to a file and read it via file tools.

### Typical workflow chain
A recommended sequence for most IDE-assisted tasks:
1. **Locate**: `find_files_by_name_keyword` / `find_files_by_glob` → `open_file_in_editor`
2. **Understand**: `get_file_text_by_path` + `search_in_files_by_text` as needed
3. **Modify**: `replace_text_in_file` for textual changes; `rename_refactoring` for renames
4. **Format & check**: `reformat_file` (if needed) → `get_file_problems` (per modified file)
5. **Run**: `get_run_configurations` → `execute_run_configuration`

## Troubleshooting

When JetBrains MCP connection fails, check in order:
1. Is JetBrains IDE open with the target project?
2. Is the MCP plugin enabled and running?
3. If using 1mcp: is `jetbrains` server enabled in `mcp.json` (`disabled: false`)?
4. If using 1mcp: run `./agent-tool.sh cfg 1mcp restart` to apply config changes
5. Is the endpoint URL correct? (SSE default: `http://localhost:64343/sse`)

## References
- notes + tool list (condensed): `skills/jetbrains-skill/references/jetbrains-skill.md`