home / mcp / jetbrains mcp bridge mcp server
Bridges JetBrains IDE tooling to Cascade Windsurf via MCP enabling seamless IDE tooling integration.
Configuration
View docs{
"mcpServers": {
"codecraftingdevelopment-codecraftingdevelopment-mcp-jetbrain": {
"command": "node",
"args": [
"C:/Users/chris/IdeaProjects/test/dist/mcp-server.js"
],
"env": {
"JETBRAINS_MCP_HOST": "127.0.0.1",
"JETBRAINS_MCP_PORT": "64342"
}
}
}
}You can use the JetBrains MCP Bridge to connect JetBrains IDE tooling with Cascade Windsurf through MCP. This bridge lets you access JetBrains tooling inside your MCP workflow, providing a smooth development experience across IDEs and client tools.
Set up the MCP bridge in your Windsurf environment, then start the local MCP server. From your JetBrains IDE, enable the MCP plugin and connect to the local proxy. Once the proxy is active (default port 64342), Cascade and Windsurf will expose the JetBrains tools through the MCP channel, letting you use IDE features directly in your workflow.
Prerequisites you need before installation:
Install dependencies and build the MCP server with the following commands. Run each command on its own line.
npm install
npm run build:mcpConfigure the Windsurf MCP server to point to the JetBrains MCP bridge. Use the following configuration snippet in your Windsurf MCP config file.
{
"mcpServers": {
"jetbrains": {
"command": "node",
"args": ["C:/Users/chris/IdeaProjects/test/dist/mcp-server.js"],
"env": {
"JETBRAINS_MCP_HOST": "127.0.0.1",
"JETBRAINS_MCP_PORT": "64342"
}
}
}
}The following environment variables control the JetBrains MCP bridge. You can set them in your shell or within the Windsurf config as shown above.
JETBRAINS_MCP_HOST=127.0.0.1
JETBRAINS_MCP_PORT=64342You can manually start the MCP bridge with the provided npm script to verify the setup.
npm run start:mcpIf you want a web interface to test the MCP connection, you can run the development server and open the browser to inspect available MCP tools.
npm run dev
```
Open http://localhost:5173 to view the MCP tools.Install project dependencies required for the MCP bridge.
Build the MCP bridge bundle used by the local stdio server.
Start the MCP bridge server for local testing and usage.
Run the development web interface to test and inspect MCP tools.