JetBrains/mcp-jetbrains

**This repository is no longer maintained.** The core functionality has been integrated into all IntelliJ-based IDEs since version 2025.2.
The built-in functionality works with SSE and JVM-based proxy (for STDIO) so this NPM package is no longer required.
**Migration:** Please refer to the official documentation for details on using the built-in functionality.
**Issues & Support:** For bugs or feature requests related to the built-in MCP functionality, please use the JetBrains YouTrack%7D%20).
JetBrains MCP Proxy Server
The server proxies requests from client to JetBrains IDE.
Install MCP Server plugin
https://plugins.jetbrains.com/plugin/26071-mcp-server
VS Code Installation
For one-click installation, click one of the install buttons below:
Manual Installation
Add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).
Optionally, you can add it to a file called .vscode/mcp.json in your workspace:
Usage with Claude Desktop
To use this with Claude Desktop, add the following to your claude_desktop_config.json.
The full path on MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json, on Windows: %APPDATA%/Claude/claude_desktop_config.json.
After installing the MCP Server Plugin, and adding the JSON to the config file, restart Claude Desktop, and make sure the Jetbrains product is open before restarting Claude Desktop.
Configuration
If you're running multiple IDEs with MCP server and want to connect to the specific one, add to the MCP server configuration:
By default, we connect to IDE on 127.0.0.1 but you can specify a different address/host:
To enable logging add:
Troubleshooting
Node.js Version Requirements
**Problem:** Error message: Cannot find module 'node:path'
**Solution:**
MCP Proxy doesn't work on Node 16.
Upgrade your Node.js installation to version 18 or later. Make sure that command in config points to the correct Node.js version.
Try to use the full path to the latest version of NodeJS.
MacOS: Plugin Unable to Detect Node.js Installed via nvm
**Problem:** On MacOS, if you have Node.js installed through nvm (Node Version Manager), the MCP Server Plugin might be unable to detect your Node.js installation.
**Solution:** Create a symbolic link in /usr/local/bin pointing to your nvm npx executable:
This one-liner checks if npx exists in your path and creates the necessary symbolic link with proper permissions.
Using MCP with External Clients or Docker Containers (LibreChat, Cline, etc.)
**Problem:** When attempting to connect to the JetBrains MCP proxy from external clients, Docker containers, or third-party applications (like LibreChat), requests to endpoints such as http://host.docker.internal:6365/api/mcp/list_tools may return 404 errors or fail to connect.