JetBrains IDEs MCP — Anwendungsfälle, Installieren & Live-Demo

Name: JetBrains IDEs MCP Server
Author: JetBrains

Warum nutzen

Hauptfunktionen

Reads the IDE's indexed model — symbol resolution, type info, call hierarchies
Trigger refactorings, run configurations, tests from the agent
Works across all IntelliJ-based IDEs with the same MCP Server plugin
Note: since 2025.2, MCP Server is integrated into the IDEs natively

Live-Demo

In der Praxis

jetbrains.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": [
        "-y",
        "@jetbrains/mcp-proxy"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": [
        "-y",
        "@jetbrains/mcp-proxy"
      ]
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": [
        "-y",
        "@jetbrains/mcp-proxy"
      ]
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": [
        "-y",
        "@jetbrains/mcp-proxy"
      ]
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "jetbrains",
      "command": "npx",
      "args": [
        "-y",
        "@jetbrains/mcp-proxy"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "jetbrains": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@jetbrains/mcp-proxy"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add jetbrains -- npx -y @jetbrains/mcp-proxy

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: JetBrains IDEs

Rename a symbol safely across the whole project

👤 Java / Kotlin / Python / C# engineers ⏱ ~10 min intermediate

Wann einsetzen: You want to rename a symbol but grep-and-replace would miss string references or dynamic calls.

Voraussetzungen

MCP Server plugin installed in the IDE — plugins.jetbrains.com/plugin/26071-mcp-server — or built-in if on 2025.2+
Project opened and indexed in the IDE — Open the project; wait for indexing to complete (status bar)

Ablauf

Find the symbol

Find the definition and all usages of getCurrentUser in the project. Include test files.✓ Kopiert

→ IDE-accurate usage list with file:line
Dry-run the rename

Show me what renaming to getAuthenticatedUser would change. Flag any string literals or reflection-based calls I'll need to fix manually.✓ Kopiert

→ Preview diff + manual-fix list
Apply the refactor

Apply the rename. Then run the affected tests.✓ Kopiert

→ Refactor done, tests green

Ergebnis: A safe rename with IDE-level accuracy, covered by the IDE's existing refactoring engine.

Fallstricke

Reflection-based or string-built references aren't caught — After refactor, grep for the old name as a string — the IDE warns but doesn't auto-fix these
IDE not fully indexed, results are partial — Wait for the progress bar to clear before running; ask the IDE for index status first

Kombinieren mit: git

Run a specific test and iterate on failures

👤 Any engineer using JetBrains IDEs ⏱ ~15 min intermediate

Wann einsetzen: You want the agent to write code, run the matching test, fix failures, iterate — without leaving the chat.

Voraussetzungen

Run configuration for the test exists in the IDE — Right-click test file → Run — IDE saves the config

Ablauf

Run the specific test

Run the CartCalculatorTest class. Return pass/fail per method with failure messages.✓ Kopiert

→ Structured test result
Fix failures

For each failing test, read the source, identify the bug, propose a minimal fix.✓ Kopiert

→ File:line + proposed change
Loop

Apply the fix and re-run until green. Don't modify tests, only production code.✓ Kopiert

→ All tests passing

Ergebnis: TDD-at-agent-speed with the IDE's compile + run infrastructure.

Fallstricke

Agent modifies tests to make them pass — Explicit prompt: 'do not touch test files'; review the diff before committing

Onboard to an unfamiliar codebase via IDE navigation

👤 New hires, code reviewers ⏱ ~30 min beginner

Wann einsetzen: You need to understand how X is used without bouncing around 20 files manually.

Ablauf

Start at an entrypoint

Find the HTTP handler for POST /checkout. Show me the call hierarchy — what it calls, depth 3.✓ Kopiert

→ Call tree with file:line nodes
Find tests

Find all tests that exercise the checkout flow. Open each and summarize what they cover.✓ Kopiert

→ Test coverage map
Explain the flow

Write a 1-page explainer: endpoint → validation → payment → persistence → response. Reference files with line numbers.✓ Kopiert

→ Onboarding-quality explainer

Ergebnis: A concrete mental model of a subsystem in 30 minutes instead of a day.

Fallstricke

Agent invents class/method names that don't exist — Every claim must link to file:line — if it can't, it's hallucinated; call it out and re-query

Kombinieren mit: git

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

jetbrains + git

IDE-level refactor + verify commit is clean

Rename fetchUser to loadUser project-wide. Then show me the git diff — confirm tests still pass and commit.✓ Kopiert

jetbrains + github

Reviewing a PR with IDE navigation instead of GitHub's web UI

Check out PR #234's branch. Walk through the diff using find_usages to understand what each changed method is called from.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
get_project_structure		Overview when starting in a new project	free
find_usages	symbol	Impact analysis before changes	free
search_in_files	text, scope?	Full-text search across project	free
get_symbol_info	symbol or file:line	Resolve what something is	free
run_configuration	config_name	Execute a saved run config (test, app, script)	free (local)
apply_refactoring	refactor type + params	Rename, extract method, inline, move	free
get_diagnostics	file_path?	Catch issues the IDE already knows about	free

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None — local IDE
Tokens pro Aufruf: Call hierarchies can be large; limit depth explicitly
Kosten in €: Free — MCP is free; you need a JetBrains license anyway
Tipp: Rely on IDE operations (find_usages, refactor) over raw filesystem reads — cheaper tokens and more accurate

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None — local IDE

Datenabfluss: None to JetBrains; MCP is localhost-only between IDE and client

The JetBrains/mcp-jetbrains npm package is deprecated — since IDE 2025.2, MCP Server functionality is built in. Prefer the built-in version if you're on a recent release.

Fehlerbehebung

Häufige Fehler und Lösungen

Connection refused / MCP can't reach IDE

The IDE must be open with the plugin enabled. Check Settings → Tools → MCP Server; port is usually 63342 or auto-assigned.

Prüfen: curl http://localhost:63342/api/mcp

Tools return 'Project not found'

No project open in the IDE, or multiple projects open and agent is asking about the wrong one. Focus the correct window.

Refactor reports files changed but they look the same

IDE buffers aren't saved to disk yet. Call a 'save all' tool or Cmd+S in the IDE.

find_usages misses references

Indexing hasn't completed. Wait for the IDE status bar to show 'Indexing complete'.

Alternativen

JetBrains IDEs vs. andere

Alternative	Wann stattdessen	Kompromiss
VSCode MCP (various community)	You're on VSCode instead of JetBrains	Different IDE, different ecosystem — not a direct swap
language-server MCPs	You want IDE-agnostic code intelligence via LSP	LSP gives basic symbol info but not refactoring or run configs

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen