Server facts
JetBrains MCP Proxy Server
Project
- Author
- JetBrains
- Repository
- github.com/JetBrains/mcp-jetbrains
- License
- Apache-2.0
- Category
- Developer Tools
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 963
- Last commit
- Data as of
Tags
- Deprecated
- Ide Integration
- Jetbrains
- Mcp Proxy
Overview
JetBrains MCP Proxy Server is a legacy connection layer between an MCP client and a JetBrains IDE. The documented setup pairs an npm proxy with the IDE's MCP Server plugin, letting clients such as Claude Desktop or VS Code forward requests into the running development environment. The README concentrates on establishing that connection, not on listing individual IDE tools or their schemas. It therefore provides a bridge configuration rather than a catalog of available development actions.
The repository now carries an explicit deprecation notice and is no longer maintained. JetBrains integrated the core capability into IntelliJ-based IDEs beginning with version 2025.2. That built-in implementation supports SSE and a JVM proxy for stdio, making this npm package unnecessary for the newer path. The README directs users to official documentation for migration and to YouTrack for issues concerning the integrated implementation. This maintenance status is the main consideration before choosing the legacy package.
For existing installations, the proxy launches through npx and requires Node.js 18 or later. The IDE must be open, and the plugin must be installed. Optional environment settings select an IDE port, change the destination host, or enable logs. External clients and containers need additional IDE connection settings and an explicit network address. macOS users with nvm may also need to make the npx executable discoverable to the plugin.
Install & configure
Requirements
- Node.js 18 or newer
- JetBrains IDE with the MCP Server plugin installed
- The target IDE open before restarting the MCP client
npx -y @jetbrains/mcp-proxyThis is the deprecated npm-proxy configuration. For IntelliJ-based IDEs 2025.2 and later, follow the linked JetBrains documentation for the built-in MCP integration instead.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"mcp-jetbrains": {
"command": "npx",
"args": [
"-y",
"@jetbrains/mcp-proxy"
],
"env": {
"IDE_PORT": "<optional port of the target IDE>",
"HOST": "<optional IDE host address>",
"LOG_ENABLED": "<optional true to enable logging>"
}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"mcp-jetbrains": {
"command": "npx",
"args": [
"-y",
"@jetbrains/mcp-proxy"
],
"env": {
"IDE_PORT": "<optional port of the target IDE>",
"HOST": "<optional IDE host address>",
"LOG_ENABLED": "<optional true to enable logging>"
}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"mcp-jetbrains": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@jetbrains/mcp-proxy"
],
"env": {
"IDE_PORT": "<optional port of the target IDE>",
"HOST": "<optional IDE host address>",
"LOG_ENABLED": "<optional true to enable logging>"
}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"mcp-jetbrains": {
"command": "npx",
"args": [
"-y",
"@jetbrains/mcp-proxy"
],
"env": {
"IDE_PORT": "<optional port of the target IDE>",
"HOST": "<optional IDE host address>",
"LOG_ENABLED": "<optional true to enable logging>"
}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"mcp-jetbrains": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@jetbrains/mcp-proxy"
],
"env": {
"IDE_PORT": "<optional port of the target IDE>",
"HOST": "<optional IDE host address>",
"LOG_ENABLED": "<optional true to enable logging>"
}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
No individual tool names were confirmed in the source material. Check the repository for its current tool list.
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Maintain an existing Claude Desktop connection to a legacy JetBrains MCP plugin.
- Configure a VS Code MCP client to reach a running JetBrains IDE.
- Select a particular IDE instance when several are open.
Strengths
- Documents configurations for Claude Desktop and VS Code.
- Allows explicit host and IDE-port selection.
- Includes troubleshooting for Node discovery and external connections.
Limitations
- Deprecated and no longer maintained.
- Newer IntelliJ-based IDEs use the integrated implementation instead.
- No individual tool list is provided in the README.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
