JetBrains IDE WebSocket Monitor

by dortegau

1 stars
263 downloads
Not rated
GitHub

About

JetBrains MCP Server fork that broadcasts real-time WebSocket monitoring of all tool calls between clients and IDEs for debugging and extending integration functionality.

Details

Author
dortegau
Repository
dortegau/mcp-proxy-sidecar
GitHub stars
1
Downloads
263
License
Apache License 2.0
Categories
Developer Tools, AI, Infrastructure, Knowledge Base

This fork adds WebSocket notifications that allow you to monitor all MCP tool calls in real-time. Each tool call is broadcasted through WebSocket with detailed information about the endpoint and arguments.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name JetBrains IDE WebSocket Monitor
    Command (node, npx, python, etc.) npx
    Arguments
    • Argument 1 -y
    • Argument 2 mcp-proxy-sidecar
    Environment
    • HOST 127.0.0.1
    • WS_PORT 27042
    • IDE_PORT 63342
    • LOG_ENABLED true

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

The WebSocket server runs on port 27042 by default. You can customize this port using the WS_PORT environment variable in your configuration:

"env": {
  "WS_PORT": "<custom port number>"  // Example: "8080"
}

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "jetbrains ide websocket monitor": {
            "env": {
                "HOST": "127.0.0.1",
                "WS_PORT": "27042",
                "IDE_PORT": "63342",
                "LOG_ENABLED": "true"
            },
            "args": [
                "-y",
                "mcp-proxy-sidecar"
            ],
            "command": "npx"
        }
    }
}

Linux

{
    "env": {
        "HOST": "127.0.0.1",
        "WS_PORT": "27042",
        "IDE_PORT": "63342",
        "LOG_ENABLED": "true"
    },
    "args": [
        "-y",
        "mcp-proxy-sidecar"
    ],
    "command": "npx"
}

Macos

{
    "env": {
        "HOST": "127.0.0.1",
        "WS_PORT": "27042",
        "IDE_PORT": "63342",
        "LOG_ENABLED": "true"
    },
    "args": [
        "-y",
        "mcp-proxy-sidecar"
    ],
    "command": "npx"
}

Windows

{
    "env": {
        "HOST": "127.0.0.1",
        "WS_PORT": "27042",
        "IDE_PORT": "63342",
        "LOG_ENABLED": "true"
    },
    "args": [
        "/c",
        "npx",
        "-y",
        "mcp-proxy-sidecar"
    ],
    "command": "cmd"
}

MCP Proxy Sidecar

npm version
License
Publish to NPM

A fork of the JetBrains MCP Server that adds WebSocket monitoring capabilities, created by @dortegau.

> This project extends the original MCP server functionality with WebSocket support while maintaining compatibility with all features of the original implementation.

Architecture

graph LR
    A[MCP Client<br>e.g. Claude<br>Desktop App]
    B[MCP Proxy<br>Sidecar<br>with WebSocket]
    C[JetBrains IDE]
    D[WebSocket Clients<br>Monitoring]
    
    A <--MCP requests/responses--> B
    B <--IDE commands/responses--> C
    B --WebSocket notifications<br>port 27042--> D

style A fill:#f5f5f5,stroke:#333,stroke-width:2px
style B fill:#e1f5fe,stroke:#333,stroke-width:2px
style C fill:#f5f5f5,stroke:#333,stroke-width:2px
style D fill:#f5f5f5,stroke:#333,stroke-width:2px

The diagram above illustrates the system architecture and data flow:
1. MCP Clients (like Claude Desktop App) communicate with the Sidecar using MCP protocol
2. The Sidecar translates and forwards commands to JetBrains IDE
3. Responses from the IDE are sent back through the Sidecar
4. All tool calls are broadcasted via WebSocket for monitoring purposes

Features

This fork adds WebSocket notifications that allow you to monitor all MCP tool calls in real-time. Each tool call is broadcasted through WebSocket with detailed information about the endpoint and arguments.

WebSocket Message Format

interface MCPNotification {
  type: 'mcp-notification';
  payload: {
    endpoint: string;     // Tool name that was called
    content: any;         // Call arguments
    timestamp: string;    // ISO timestamp
  }
}

WebSocket Configuration

The WebSocket server runs on port 27042 by default. You can customize this port using the WS_PORT environment variable in your configuration:
"env": {
  "WS_PORT": "<custom port number>"  // Example: "8080"
}

Usage

Install MCP Server Plugin

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.