Monitor all JetBrains IDE WebSocket tool calls in real time for advanced debugging and integration with JetBrains IDE We
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
Provide Claude with access to relevant context and data
Example: Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
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
Time estimate: 15-60 minutes depending on server complexity
Prerequisites
Vertiso Memory
Portable, durable memory for every AI agent you use
Promptless
Search, read, and edit your documentation
Tines 3B
Create, test, and ship apps, agents, and automations on Tines 3B without leaving Claude.
MuuMuu Domain byGMO Pepabo
ムームードメインと接続し、ドメインの空き検索・価格確認から購入手続きまでを会話で進められます。決済はムームードメインのサイト上でご自身が完了させる方式です。保有ドメインの一覧・詳細確認、ネームサーバーの確認・変更、DNSレコードの一覧・作成・更新・削除、更新日や自動更新設定の確認・変更にも対応します。
OnChainDiligence
Inspect autonomous payments before execution and independently verify evidence afterward.
Vaisala Xweather
JetBrains IDE WebSocket Monitor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend JetBrains IDE WebSocket Monitor for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated JetBrains IDE WebSocket Monitor against two servers with overlapping tools; this profile had the clearer scope statement.
JetBrains IDE WebSocket Monitor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: JetBrains IDE WebSocket Monitor is the kind of server we cite when onboarding engineers to host + tool permissions.
I recommend JetBrains IDE WebSocket Monitor for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
JetBrains IDE WebSocket Monitor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
JetBrains IDE WebSocket Monitor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Strong directory entry: JetBrains IDE WebSocket Monitor surfaces stars and publisher context so we could sanity-check maintenance before adopting.
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
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"ide": {
"command": "npx",
"args": [
"-y",
"mcp-proxy-sidecar"
],
"env": {
"WS_PORT": "27042"
}
}
}
}Adds WebSocket monitoring to JetBrains IDE MCP integration, broadcasting all tool calls between MCP clients and IDEs in real-time for debugging purposes.
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.
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.
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.
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:
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.
interface MCPNotification {
type: 'mcp-notification';
payload: {
endpoint: string; // Tool name that was called
content: any; // Call arguments
timestamp: string; // ISO timestamp
}
}
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"
}
https://plugins.jetbrains.com/plugin/26071-mcp-server
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
}
}
}
}
The following environment variables can be configured in your claude_desktop_config.json:
| Variable | Description | Default |
|---|---|---|
WS_PORT | Port for WebSocket server | 27042 |
IDE_PORT | Specific port for IDE connection | Auto-scans 63342-63352 |
HOST | Host address for IDE connection | 127.0.0.1 |
LOG_ENABLED | Enable debug logging | false |
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.
pnpm install --frozen-lockfile
pnpm build
git checkout -b feature/amazing-feature)git commit -m 'Add some amazing feature')git push origin feature/amazing-feature)This package is published to npm with:
To publish a new version:
This is a fork of the JetBrains MCP Proxy Server. All credit for the original implementation goes to the JetBrains team.
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ 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.
Access real-time, forecast, and historical weather.