mcp-jetbrains

This MCP server acts as a proxy between MCP clients and JetBrains IDEs. It forwards MCP protocol requests from a client (such as an external tool, VS Code configuration, Claude Desktop, or a custom client) to the JetBrains IDE’s built-in MCP proxy endpoints, allowing you to access tools and features provided by JetBrains MCP without embedding the logic in each client. The server is intended to be run via npx using the JetBrains MCP Proxy package and can be configured with environment variables to point to the IDE's host and port. It supports external connections when you configure the IDE to accept them and when you specify the IDE's LAN address and port in the env/config. Typical usage involves starting the proxy and then pointing your MCP client to the proxy’s host/port, with the IDE_PORT and HOST values directing the proxy to the running IDE instance.

Prerequisites:

• Node.js 18 or later (the MCP proxy may not work reliably on Node 16).
• Internet access to fetch npm packages.

Installation steps:

1. Ensure Node.js is installed (version 18+).
2. Run the MCP proxy via npx (no permanent install necessary):

npx -y @jetbrains/mcp-proxy

3. Optionally, install globally for convenience (not required):

npm install -g @jetbrains/mcp-proxy

4. Create a simple config (example shown in usage) to start the proxy with the desired IDE connection parameters. For example, in your environment:

IDE_PORT=XXXX HOST=YOUR_IP npx -y @jetbrains/mcp-proxy

5. If you plan to run from within VS Code or Claude Desktop, copy the config snippet from the README into your settings or config file as shown in the examples.

Notes and tips:

• This MCP server is deprecated. JetBrains built-in MCP functionality is now integrated into IntelliJ-based IDEs as of 2025.2, and the standalone MCP server package is no longer required for typical workflows.
• If using external clients or containers, ensure the IDE allows external connections and use the IDE's LAN IP and port (not host.docker.internal) in your configuration.
• Node.js version compatibility issues may arise (errors like Cannot find module 'node:path' indicate Node 16 is too old; upgrade to Node 18+ and point the command to the correct node version).
• On macOS with nvm-installed Node.js, you may need to create a symlink for npx: which npx &>/dev/null && sudo ln -sf "$(which npx)" /usr/local/bin/npx
• When wiring to external clients (Docker, LibreChat, etc.), set IDE_PORT and HOST to the IDE's listening port and LAN address respectively, and enable external connections in the IDE settings.
• The recommended usage for VS Code manual installation relies on the JSON blocks shown in the README; ensure you adjust the server key if you have multiple IDEs or workspaces.