How jetbrains/mcp-jetbrains works
This small Node.js MCP proxy exposes JetBrains IDE tools to clients over stdio. It discovers and periodically refreshes the IDE endpoint, lists available tools, and forwards tool calls and results. The implementation is concentrated in src/index.ts; the README also documents configurable host/port selection and optional logging. The graph reflects the sampled source and documented client workflow, not IDE-side implementation details.
Main entry points: index.ts MCP Proxy
Components 5
Other components
- MCP Client
- MCP Proxy
src/index.ts - Endpoint Discovery
src/index.ts - IDE MCP API
- Optional Logging
src/index.ts
Connections 10
- MCP Client → MCP Proxy: stdio requests
- MCP Proxy → Endpoint Discovery: refreshes endpoint
- Endpoint Discovery → IDE MCP API: probes tools
- IDE MCP API → Endpoint Discovery: returns probe response
- MCP Proxy → IDE MCP API: lists tools
- IDE MCP API → MCP Proxy: returns tool list
- MCP Proxy → IDE MCP API: forwards tool call
- IDE MCP API → MCP Proxy: returns tool result
- MCP Proxy → MCP Client: returns MCP response
- MCP Proxy → Optional Logging: writes diagnostics