MCP Directory

JetBrains MCP Proxy

Official

Connect MCP clients to a running JetBrains IDE (IntelliJ, PyCharm, WebStorm, Android Studio).

Verified
stdio (local)
No auth
TypeScript
View repo 5.0k Website npm

Add to your client

Copy the config for your MCP client and paste it into its config file.

Install / run
npx -y @jetbrains/mcp-proxy

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

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

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

Before you start

  • Node.js 18 or later (Node 16 is not supported)
  • A running JetBrains IDE (IntelliJ IDEA, PyCharm, WebStorm, GoLand, Android Studio, etc.)
  • The JetBrains 'MCP Server' plugin installed from the Marketplace (for IDE versions before 2025.2; in 2025.2+ the functionality is built in)
  • No API key or token is required — the proxy connects to the IDE on localhost

About JetBrains MCP Proxy

The JetBrains MCP Proxy is a small Node.js stdio server that bridges an MCP client (Claude Desktop, VS Code, Cursor, etc.) to a running JetBrains IDE such as IntelliJ IDEA, PyCharm, WebStorm, GoLand, or Android Studio. It forwards MCP requests to the IDE's built-in MCP web server, giving the assistant access to your live IDE session, not just files on disk.

Through the IDE it can read the file currently open in the editor and its path, read/replace file contents by path, create files, list open files, search files and commits, retrieve breakpoints, and execute commands in the integrated terminal, among other actions. The exact set of exposed tools is controlled inside the IDE under Settings > Tools > MCP Server > Exposed Tools, where you can enable or disable individual capabilities.

Important: this proxy is effectively deprecated. JetBrains has integrated MCP server functionality natively into all IntelliJ-based IDEs since version 2025.2, so on recent IDEs you no longer need this separate proxy. It remains useful for older IDE versions or clients that connect to the proxy command. It requires no credentials because it talks to a local IDE over 127.0.0.1.

Tools & capabilities (10)

get_open_in_editor_file_text

Return the full text of the file currently open in the editor

get_open_in_editor_file_path

Return the absolute path of the currently open file

get_file_text_by_path

Read the contents of a file by its path

replace_file_text_by_path

Replace the contents of a file at a given path

create_new_file_with_text

Create a new file with the supplied content

list_files_in_folder

List files in a folder / list currently open files

search_in_files_content

Search the project for text/files by name

execute_terminal_command

Run a shell command in the IDE's integrated terminal

get_all_breakpoints

Retrieve the breakpoints currently set in the IDE

execute_action_by_id

Invoke an IDE action by its identifier

When to use it

  • Use it when you want an assistant to act on the exact file you currently have open in your JetBrains IDE
  • Use it when you need the assistant to run terminal commands, builds, or tests inside the IDE's environment
  • Use it when searching project files or commit history and applying edits through the IDE rather than the raw filesystem
  • Use it when working in Android Studio or another IntelliJ-based IDE older than 2025.2 that lacks native MCP
  • Use it when you want IDE-aware context (open files, breakpoints) surfaced to your MCP client

Quick setup

  1. 1Update to a recent JetBrains IDE; on 2025.2+ enable the built-in MCP server in the IDE settings instead of this proxy
  2. 2For older IDEs, install the 'MCP Server' plugin from the JetBrains Marketplace and restart the IDE
  3. 3Add the proxy to your MCP client config with command `npx -y @jetbrains/mcp-proxy`
  4. 4Optionally set IDE_PORT (to target a specific IDE instance), HOST, or LOG_ENABLED=true
  5. 5Restart your MCP client and confirm the JetBrains tools appear
  6. 6Verify by asking the assistant for the path or text of your currently open file

Security notes

The proxy can drive the IDE to read and modify files and run code in your open project, so only connect trusted clients. On IDE 2025.2+ prefer the built-in MCP server over this bridge.

JetBrains MCP Proxy FAQ

Is this proxy still needed?

On IntelliJ-based IDEs version 2025.2 and later, no — MCP server functionality is built into the IDE and configured via AI Assistant settings. The standalone proxy is mainly for older IDE versions.

Does it require an API key?

No. The proxy connects to your running IDE over localhost (127.0.0.1), so there are no credentials to configure.

How does it pick which IDE instance to connect to?

It auto-detects the IDE's built-in web server port; if you run multiple IDEs you can set the IDE_PORT environment variable to target a specific one.

Why won't it start on Node 16?

The proxy requires Node.js 18 or later. Upgrade your Node runtime; Node 16 is explicitly unsupported.

Which IDEs are supported?

All IntelliJ-based IDEs — IntelliJ IDEA, PyCharm, WebStorm, GoLand, PhpStorm, RubyMine, CLion, Rider — plus Android Studio.

#jetbrains#official#ide#intellij#developer-tools

Alternatives to JetBrains MCP Proxy

Compare all alternatives →
Playwright MCP Server
Developer Tools
24k

Microsoft's official browser-automation MCP using Playwright's accessibility tree (no vision model).

Featured
Verified
stdio (local)
No auth
TypeScript
12 tools
Updated 9 days agoRepo
Context7 MCP Server
Developer Tools
28k

Up-to-date, version-specific library documentation injected into your coding agent.

Verified
stdio (local)
API key
TypeScript
2 tools
Updated 13 days agoRepo
Serena
Developer Tools
12k

LSP-powered coding agent toolkit: semantic symbol search, references and structural edits.

Verified
stdio (local)
No auth
Python
11 tools
Updated 11 days agoRepo

Compare JetBrains MCP Proxy with:

vs Playwright MCP Servervs Context7 MCP Servervs Serenavs GitMCP