developer-tools

JetBrains IDE WebSocket Monitor

dortegau

by dortegau

Monitor all JetBrains IDE WebSocket tool calls in real time for advanced debugging and integration with JetBrains IDE We

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

github stars

1

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Real-time WebSocket monitoringFork of official JetBrains MCP server

best for

  • / Debugging MCP integrations with JetBrains IDEs
  • / Monitoring IDE automation workflows
  • / Extending MCP functionality with custom tooling

capabilities

  • / Monitor MCP tool calls via WebSocket
  • / Proxy MCP requests between clients and JetBrains IDEs
  • / Broadcast real-time notifications on port 27042
  • / Maintain full compatibility with original JetBrains MCP server

what it does

Adds WebSocket monitoring to JetBrains IDE MCP integration, broadcasting all tool calls between MCP clients and IDEs in real-time for debugging purposes.

about

JetBrains IDE WebSocket Monitor is a community-built MCP server published by dortegau that provides AI assistants with tools and capabilities via the Model Context Protocol. Monitor all JetBrains IDE WebSocket tool calls in real time for advanced debugging and integration with JetBrains IDE We It is categorized under developer tools.

how to install

You can install JetBrains IDE WebSocket Monitor in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

Apache-2.0

JetBrains IDE WebSocket Monitor is released under the Apache-2.0 license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

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

https://plugins.jetbrains.com/plugin/26071-mcp-server

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.

{
  "mcpServers": {
    "ide": {
      "command": "npx",
      "args": ["-y", "mcp-proxy-sidecar"],
      "env": {
        "WS_PORT": "27042"  // Optional: customize WebSocket port
      }
    }
  }
}

Configuration Options

The following environment variables can be configured in your claude_desktop_config.json:

VariableDescriptionDefault
WS_PORTPort for WebSocket server27042
IDE_PORTSpecific port for IDE connectionAuto-scans 63342-63352
HOSTHost address for IDE connection127.0.0.1
LOG_ENABLEDEnable debug loggingfalse

Example configuration with all options:

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

Note: If IDE_PORT is not specified, the sidecar will automatically scan ports 63342-63352 to find the IDE.

Development

Requirements

  • Node.js 20.x
  • pnpm (latest version)

Build

  1. Install dependencies:
    pnpm install --frozen-lockfile
    
  2. Build the project:
    pnpm build
    

Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Publishing

This package is published to npm with:

  • Provenance enabled for supply chain security
  • Automated releases via GitHub Actions when creating a new release
  • Public access on npm registry

To publish a new version:

  1. Update version in package.json
  2. Create and push a new tag matching the version
  3. Create a GitHub release from the tag
  4. The workflow will automatically build and publish to npm

Changelog

1.0.0

  • Initial fork from @jetbrains/mcp-proxy
  • Added WebSocket support for real-time tool call monitoring
  • Renamed package for clarity
  • Updated documentation and configuration examples

Credits

This is a fork of the JetBrains MCP Proxy Server. All credit for the original implementation goes to the JetBrains team.

FAQ

What is the JetBrains IDE WebSocket Monitor MCP server?
JetBrains IDE WebSocket Monitor is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for JetBrains IDE WebSocket Monitor?
This profile displays 38 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.738 reviews
  • Dhruvi Jain· Dec 24, 2024

    JetBrains IDE WebSocket Monitor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Charlotte Smith· Dec 24, 2024

    I recommend JetBrains IDE WebSocket Monitor for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Ren Martinez· Dec 20, 2024

    We evaluated JetBrains IDE WebSocket Monitor against two servers with overlapping tools; this profile had the clearer scope statement.

  • Min Martinez· Dec 16, 2024

    JetBrains IDE WebSocket Monitor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Kaira Mensah· Dec 12, 2024

    Useful MCP listing: JetBrains IDE WebSocket Monitor is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Oshnikdeep· Nov 15, 2024

    I recommend JetBrains IDE WebSocket Monitor for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Jin Martinez· Nov 15, 2024

    JetBrains IDE WebSocket Monitor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Min Khan· Nov 11, 2024

    JetBrains IDE WebSocket Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Hiroshi Lopez· Nov 3, 2024

    Strong directory entry: JetBrains IDE WebSocket Monitor surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Kiara Garcia· Oct 22, 2024

    I recommend JetBrains IDE WebSocket Monitor for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

showing 1-10 of 38

1 / 4