JetBrains MCP Proxy: Use the built-in path from 2025.2; this package is only for older IDEs

Who it's for

For people still on an older JetBrains IDE who need to proxy MCP client requests to the IDE. The evidence states: this server proxies client requests to a JetBrains IDE.

But this repository is no longer maintained. The core capability has been integrated into all IntelliJ-based IDEs since 2025.2: built-in SSE support, plus a JVM proxy for STDIO, so this NPM package is no longer needed. If your IDE is already 2025.2 or newer, do not install this package.

Continue only if you explicitly still need the historical NPM path. You also need the MCP Server plugin, and Node.js must be 18 or higher. The evidence does not list client products; coverage stops at "JetBrains IDE".

First try in 3 minutes

If the IDE ≥ 2025.2: the main path is the IDE's built-in MCP (SSE / JVM STDIO proxy). Stop there; do not run the npx below.

If you still use this package, configure:

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

And install the plugin: https://plugins.jetbrains.com/plugin/26071-mcp-server

Prerequisites: the IDE is open; the plugin is installed; Node 18+ (Node 16 raises Cannot find module 'node:path'). The proxy connects to the IDE on 127.0.0.1 by default and will touch the local IDE and project — this is not a no-local-read setup.

Where to configure: the client MCP command / args. If you have multiple IDEs open, also add:

"env": {
  "IDE_PORT": "<port of IDE's built-in webserver>"
}

Low-risk first call: one connectivity request, asking the IDE through the proxy for read-only info about the current project (for example, which project is open). The evidence does not name tools or parameters. Do not start by editing files, running a build, or performing IDE write operations.

Success signal: the proxy process starts, and the client no longer reports that it cannot reach the IDE; with multiple IDEs open, IDE_PORT points at the one you chose. If it still hits the wrong instance, change the port first; do not assume the default is correct.

Use cases

Case 1: Attach an MCP client to a single running IDE. Use the default 127.0.0.1 and the npx config above (or the 2025.2+ built-in path). The evidence only guarantees "proxy requests to the IDE" and does not list tools. So what you can confirm is: the request reached the local IDE.

Case 2: Several MCP-enabled IDEs are open on this machine, and you need to pin one. Add IDE_PORT in the config. The evidence also says you can specify a different address/host, but the locator is truncated at "specify a different address/host:" and does not give the environment-variable name. Treat only IDE_PORT as the confirmed selection method; do not invent a host variable.

Limits

The repository is no longer maintained; on 2025.2+ use the built-in capability. The historical path depends on @jetbrains/mcp-proxy, the MCP Server plugin, and Node 18+. By default it only connects to local 127.0.0.1. There are no tool names, no permission model, and no official undo. Proxying client requests to the IDE means exposing the project and IDE capabilities to that client. The evidence does not say how to look up the port, nor security steps for non-local exposure.