{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-jetbrains","slug":"jetbrains","name":"JetBrains","type":"mcp","url":"https://github.com/JetBrains/mcp-jetbrains","page_url":"https://unfragile.ai/jetbrains","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-jetbrains__cap_0","uri":"capability://tool.use.integration.mcp.protocol.translation.to.jetbrains.ide.http.api","name":"mcp protocol translation to jetbrains ide http api","description":"Translates incoming Model Context Protocol (MCP) requests from external clients into HTTP API calls to JetBrains IDE's built-in web server running on ports 63342-63352. Uses StdioServerTransport for stdin/stdout communication with clients and node-fetch for HTTP request forwarding, implementing a bridge pattern that maps MCP protocol semantics to IDE HTTP endpoints without modifying the underlying IDE behavior.","intents":["Enable external AI clients like Claude Desktop to communicate with JetBrains IDEs using a standardized protocol","Translate MCP tool calls into IDE-native operations without requiring IDE plugin development","Bridge the gap between AI agents and IDE capabilities using protocol-level abstraction"],"best_for":["AI agent developers integrating JetBrains IDEs into multi-tool workflows","Teams deploying Claude Desktop or VS Code extensions that need IDE access","Organizations standardizing on MCP for AI-IDE communication"],"limitations":["Requires MCP Server plugin installed in target JetBrains IDE — proxy alone cannot function without it","Protocol translation adds latency for each request-response cycle due to HTTP round-trip overhead","Limited to JetBrains IDEs with MCP plugin support — does not work with other IDE families","Stdio transport is synchronous, blocking concurrent requests unless multiplexed at client level"],"requires":["Node.js 18+ (ES modules support)","JetBrains IDE (IntelliJ IDEA, PyCharm, WebStorm, etc.) with MCP Server plugin installed","IDE web server running on default port range 63342-63352 or explicitly configured IDE_PORT","@modelcontextprotocol/sdk version 1.9.0+","node-fetch version 3.3.2+"],"input_types":["MCP protocol messages (JSON-RPC 2.0 format over stdio)","Tool call requests with parameters","Resource read/write requests"],"output_types":["MCP protocol responses (JSON-RPC 2.0 format)","Tool execution results","IDE state information"],"categories":["tool-use-integration","protocol-bridge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_1","uri":"capability://automation.workflow.automatic.ide.instance.discovery.and.port.scanning","name":"automatic ide instance discovery and port scanning","description":"Dynamically discovers active JetBrains IDE instances by scanning the default port range 63342-63352 without requiring manual configuration. The proxy attempts connection to each port in sequence, detecting which IDE instances are running and their web server availability, enabling zero-config setup where the proxy automatically connects to the first available IDE or a specifically configured one via IDE_PORT environment variable.","intents":["Eliminate manual IDE port configuration for users running multiple JetBrains IDEs","Automatically detect IDE availability without requiring IDE startup scripts or configuration files","Support dynamic IDE switching when multiple instances are running on the same machine"],"best_for":["Developers working with multiple JetBrains IDE instances simultaneously","CI/CD pipelines that spawn IDE instances dynamically","Teams deploying MCP proxy in containerized environments with variable IDE availability"],"limitations":["Port scanning adds startup latency (up to 11 sequential connection attempts in worst case)","Only discovers IDEs on localhost — does not support remote IDE discovery across network","Scanning range is fixed at 63342-63352 — cannot discover IDEs on custom port ranges outside this window","No IDE instance prioritization — connects to first available port rather than selecting by IDE type or project"],"requires":["JetBrains IDE running with web server enabled on default port range","Network connectivity to localhost on ports 63342-63352","Optional: IDE_PORT environment variable to override automatic discovery"],"input_types":["Environment variable IDE_PORT (optional)","HOST environment variable (optional, defaults to localhost)"],"output_types":["Discovered IDE port number","IDE web server connection status","HTTP endpoint base URL for subsequent API calls"],"categories":["automation-workflow","configuration-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_2","uri":"capability://automation.workflow.global.cli.execution.via.npx.without.local.installation","name":"global cli execution via npx without local installation","description":"Distributes the JetBrains MCP proxy as an NPM package (@jetbrains/mcp-proxy) that can be executed globally via npx without requiring local installation or dependency management. The binary mcp-jetbrains-proxy is compiled from TypeScript to JavaScript with executable permissions, published to NPM registry with automated CI/CD, and invoked directly from command line or integrated into Claude Desktop and VS Code configurations.","intents":["Run the MCP proxy immediately without npm install or project setup","Integrate the proxy into Claude Desktop configuration with a single npx command","Update to the latest proxy version automatically when using npx"],"best_for":["Individual developers wanting quick IDE integration without project setup","Non-technical users configuring Claude Desktop for IDE access","Teams deploying MCP proxy across multiple machines with minimal overhead"],"limitations":["First execution downloads package from NPM, adding 5-30 second startup latency depending on network","Requires npm/Node.js to be installed and in system PATH — not a standalone executable","Version pinning requires explicit version specification in configuration (e.g., npx @jetbrains/mcp-proxy@1.8.0)","Global execution means proxy runs in isolation without access to local project dependencies"],"requires":["Node.js 18+ installed and available in system PATH","npm or yarn package manager","Network access to NPM registry (npmjs.com)","Appropriate shell/terminal for executing npx commands"],"input_types":["Command-line arguments (optional IDE_PORT, HOST, LOG_ENABLED)","Environment variables for configuration"],"output_types":["Executable process listening on stdio transport","MCP server ready to accept client connections"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_3","uri":"capability://automation.workflow.environment.variable.based.configuration.management","name":"environment variable-based configuration management","description":"Configures proxy behavior through environment variables (IDE_PORT, HOST, LOG_ENABLED) rather than configuration files, enabling runtime customization without code changes or recompilation. The proxy reads these variables at startup to determine IDE connection target, network binding address, and logging verbosity, supporting both development workstations and containerized deployments with different configuration needs.","intents":["Configure IDE port without modifying code or configuration files","Enable debug logging for troubleshooting MCP protocol issues","Bind proxy to specific network interfaces for container or remote deployment scenarios"],"best_for":["DevOps engineers deploying MCP proxy in containerized environments","Developers debugging MCP protocol communication issues","Teams using environment-based configuration management (Docker, Kubernetes, CI/CD)"],"limitations":["Limited configuration scope — only supports IDE_PORT, HOST, and LOG_ENABLED; no advanced options","No configuration validation — invalid values silently fall back to defaults rather than failing fast","Environment variables are process-wide, making it difficult to run multiple proxy instances with different configs in same shell","No persistent configuration — settings are lost when process terminates, requiring re-specification for each run"],"requires":["Shell or environment with ability to set environment variables","Knowledge of valid port numbers (1-65535) and hostnames for IDE_PORT and HOST"],"input_types":["IDE_PORT environment variable (integer, 1-65535, optional)","HOST environment variable (hostname/IP, optional, defaults to localhost)","LOG_ENABLED environment variable (boolean, optional)"],"output_types":["Proxy configured with specified IDE connection target","Logging output to stdout/stderr based on LOG_ENABLED setting"],"categories":["automation-workflow","configuration-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_4","uri":"capability://tool.use.integration.stdio.transport.for.mcp.protocol.communication","name":"stdio transport for mcp protocol communication","description":"Implements the Model Context Protocol using StdioServerTransport from @modelcontextprotocol/sdk, enabling bidirectional JSON-RPC 2.0 communication over standard input/output streams. This transport mechanism allows the proxy to receive MCP requests from clients (VS Code, Claude Desktop, Docker containers) and send responses back through stdio, making the proxy compatible with any MCP client that supports stdio-based servers without requiring network socket configuration.","intents":["Enable MCP clients to communicate with the proxy using standard stdio streams","Support Claude Desktop and VS Code extensions that expect stdio-based MCP servers","Avoid network port conflicts by using process stdio instead of TCP/UDP ports"],"best_for":["Local development environments where stdio communication is natural","Claude Desktop integration where stdio is the standard transport mechanism","VS Code extension development requiring MCP server integration"],"limitations":["Stdio is inherently synchronous and single-threaded — cannot multiplex concurrent requests without client-side buffering","No built-in request timeout mechanism — hung requests can block the entire stdio stream","Debugging stdio communication requires special tools (strace, process monitoring) rather than standard network debugging","Cannot be used for remote communication — stdio only works for local process-to-process communication"],"requires":["@modelcontextprotocol/sdk version 1.9.0+","MCP client that supports stdio transport (Claude Desktop, VS Code with MCP extension, etc.)","Process-level access to stdin/stdout streams"],"input_types":["JSON-RPC 2.0 messages on stdin","MCP protocol requests (initialize, call_tool, read_resource, etc.)"],"output_types":["JSON-RPC 2.0 responses on stdout","MCP protocol responses with tool results or resource data"],"categories":["tool-use-integration","protocol-bridge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_5","uri":"capability://tool.use.integration.http.client.forwarding.to.jetbrains.ide.web.server","name":"http client forwarding to jetbrains ide web server","description":"Uses node-fetch (version 3.3.2+) to make HTTP requests to the JetBrains IDE's built-in web server, translating MCP tool calls and resource requests into IDE HTTP API calls. The proxy constructs HTTP requests with appropriate endpoints, parameters, and headers based on MCP request semantics, handles HTTP responses, and converts them back into MCP protocol format for return to clients.","intents":["Forward MCP tool calls to IDE HTTP endpoints for execution","Retrieve IDE state and resource information via HTTP API","Execute IDE operations (code navigation, refactoring, analysis) through HTTP interface"],"best_for":["Developers integrating with JetBrains IDE HTTP API without direct IDE plugin development","Teams using HTTP-based IDE automation rather than IDE plugin APIs","Scenarios where IDE HTTP API is more stable than plugin APIs"],"limitations":["HTTP round-trip latency adds 50-200ms per operation compared to direct IDE plugin calls","IDE HTTP API surface may be limited compared to full IDE plugin API — not all IDE features are exposed via HTTP","No built-in request retry logic — network failures cause immediate MCP errors without automatic recovery","HTTP requests are not authenticated — relies on IDE web server running on localhost without external access controls"],"requires":["node-fetch version 3.3.2+","JetBrains IDE with HTTP web server running and accessible","Knowledge of IDE HTTP API endpoints and request/response formats"],"input_types":["MCP tool call requests with parameters","MCP resource read/write requests","IDE operation specifications"],"output_types":["HTTP responses from IDE web server","Converted MCP protocol responses","Tool execution results or resource data"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_6","uri":"capability://tool.use.integration.multi.client.integration.patterns.for.vs.code.and.claude.desktop","name":"multi-client integration patterns for vs code and claude desktop","description":"Supports multiple integration patterns enabling the proxy to work with different client types: VS Code extensions via stdio configuration, Claude Desktop via MCP server configuration in claude_desktop_config.json, and Docker containers via HTTP mode with explicit network configuration. The proxy adapts its behavior based on deployment context while maintaining consistent MCP protocol implementation across all client types.","intents":["Integrate JetBrains IDEs with Claude Desktop for AI-assisted development","Enable VS Code extensions to access JetBrains IDE capabilities","Deploy MCP proxy in containerized environments with proper network isolation"],"best_for":["Teams using Claude Desktop for AI-assisted coding with JetBrains IDEs","VS Code users wanting to leverage JetBrains IDE features through extensions","Organizations deploying MCP proxy in Docker/Kubernetes environments"],"limitations":["Each client type requires different configuration — no single configuration works for all clients","Claude Desktop integration requires manual editing of claude_desktop_config.json — no UI for configuration","VS Code integration requires extension development — proxy alone does not provide VS Code extension","Docker deployment requires explicit network configuration — default localhost binding does not work across containers"],"requires":["For Claude Desktop: Claude Desktop application installed, access to claude_desktop_config.json","For VS Code: VS Code with MCP-compatible extension, Node.js 18+","For Docker: Docker runtime, network configuration knowledge"],"input_types":["Client-specific configuration (JSON for Claude Desktop, extension config for VS Code)","Environment variables for Docker deployment"],"output_types":["MCP server process ready for client connection","IDE integration available in client application"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_7","uri":"capability://automation.workflow.typescript.to.javascript.compilation.with.executable.permissions","name":"typescript-to-javascript compilation with executable permissions","description":"Implements a build process that compiles TypeScript source code to JavaScript ES modules, sets executable permissions on the compiled binary (chmod +x), and publishes the result to NPM as a globally-executable command. The build pipeline ensures the dist/src/index.js entry point is executable and properly configured as the mcp-jetbrains-proxy binary in package.json, enabling seamless npx execution.","intents":["Build a distributable MCP proxy from TypeScript source code","Create an executable CLI command that can be run globally via npx","Maintain type safety during development while distributing JavaScript to users"],"best_for":["TypeScript developers building Node.js CLI tools","Teams maintaining MCP servers with type safety requirements","Projects requiring automated CI/CD publishing to NPM"],"limitations":["Build process requires TypeScript compiler and build tools — adds development dependency overhead","Executable permissions are Unix-specific — Windows users may experience permission issues","Source maps are not included in distribution — debugging compiled code is difficult","No minification or tree-shaking — distributed package includes all code even if unused"],"requires":["TypeScript compiler (tsc) version compatible with Node.js 18+ ES modules","Build tooling configured in package.json scripts","Unix-like environment for chmod +x (or equivalent on Windows)"],"input_types":["TypeScript source files (src/index.ts)","TypeScript configuration (tsconfig.json)"],"output_types":["Compiled JavaScript files in dist/ directory","Executable binary at dist/src/index.js","NPM package ready for publication"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_8","uri":"capability://automation.workflow.semantic.versioning.with.github.release.triggered.npm.publication","name":"semantic versioning with github release-triggered npm publication","description":"Implements automated CI/CD pipeline that publishes new versions to NPM registry when GitHub releases are created, using semantic versioning (major.minor.patch) to track compatibility and feature changes. The pipeline ensures version consistency between GitHub releases and NPM package versions, enabling users to pin specific versions in their configurations and automatically receive updates when using npx without version specification.","intents":["Publish new proxy versions to NPM automatically when releasing on GitHub","Enable users to pin specific proxy versions in Claude Desktop or VS Code configurations","Track breaking changes and features through semantic versioning"],"best_for":["Open-source projects requiring automated release management","Teams deploying MCP proxy with version pinning requirements","Organizations needing clear version history and changelog"],"limitations":["Requires GitHub Actions or similar CI/CD system — cannot be done manually","Version bumping must be done manually in package.json before creating release — no automatic version detection","NPM publication requires valid NPM authentication token in CI/CD secrets","Release process is GitHub-specific — cannot publish to alternative registries without additional configuration"],"requires":["GitHub repository with release creation permissions","CI/CD system (GitHub Actions) with NPM authentication token","Semantic versioning discipline in package.json version field"],"input_types":["GitHub release creation event","package.json version field"],"output_types":["Published NPM package at specified version","GitHub release with release notes"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-jetbrains__cap_9","uri":"capability://tool.use.integration.mcp.sdk.integration.with.protocol.compliance","name":"mcp sdk integration with protocol compliance","description":"Integrates @modelcontextprotocol/sdk version 1.9.0+ to implement full Model Context Protocol compliance, including request/response handling, tool registration, and resource management. The proxy uses the SDK's StdioServerTransport and protocol handlers to ensure compatibility with all MCP clients and proper handling of MCP semantics like tool schemas, resource URIs, and error responses.","intents":["Ensure the proxy implements MCP protocol correctly and completely","Support all MCP client types that follow the protocol specification","Leverage SDK features for tool registration and resource management"],"best_for":["Developers building MCP servers that need protocol compliance","Teams integrating with multiple MCP clients requiring standard protocol support","Projects where protocol correctness is critical for reliability"],"limitations":["SDK version pinning (1.9.0+) may lag behind latest MCP protocol updates","SDK abstractions add overhead compared to minimal protocol implementations","Limited customization of protocol behavior — SDK enforces standard semantics","SDK updates may introduce breaking changes requiring proxy code updates"],"requires":["@modelcontextprotocol/sdk version 1.9.0 or later","Node.js 18+ for ES module compatibility"],"input_types":["MCP protocol messages in JSON-RPC 2.0 format","Tool call requests with parameters","Resource read/write requests"],"output_types":["MCP protocol responses in JSON-RPC 2.0 format","Tool execution results","Resource data or acknowledgments"],"categories":["tool-use-integration","protocol-bridge"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":32,"verified":false,"data_access_risk":"high","permissions":["Node.js 18+ (ES modules support)","JetBrains IDE (IntelliJ IDEA, PyCharm, WebStorm, etc.) with MCP Server plugin installed","IDE web server running on default port range 63342-63352 or explicitly configured IDE_PORT","@modelcontextprotocol/sdk version 1.9.0+","node-fetch version 3.3.2+","JetBrains IDE running with web server enabled on default port range","Network connectivity to localhost on ports 63342-63352","Optional: IDE_PORT environment variable to override automatic discovery","Node.js 18+ installed and available in system PATH","npm or yarn package manager"],"failure_modes":["Requires MCP Server plugin installed in target JetBrains IDE — proxy alone cannot function without it","Protocol translation adds latency for each request-response cycle due to HTTP round-trip overhead","Limited to JetBrains IDEs with MCP plugin support — does not work with other IDE families","Stdio transport is synchronous, blocking concurrent requests unless multiplexed at client level","Port scanning adds startup latency (up to 11 sequential connection attempts in worst case)","Only discovers IDEs on localhost — does not support remote IDE discovery across network","Scanning range is fixed at 63342-63352 — cannot discover IDEs on custom port ranges outside this window","No IDE instance prioritization — connects to first available port rather than selecting by IDE type or project","First execution downloads package from NPM, adding 5-30 second startup latency depending on network","Requires npm/Node.js to be installed and in system PATH — not a standalone executable","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.3,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":1,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.577Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=jetbrains","compare_url":"https://unfragile.ai/compare?artifact=jetbrains"}},"signature":"+AiKiMlSgcgBTQiBEyWvbOtaLr+dtD63OpbTjTYK7iozjFllZDdXBhpC0HBLtPqJ4QYCdh69efcRlegtpMTNDw==","signedAt":"2026-06-17T22:10:20.396Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/jetbrains","artifact":"https://unfragile.ai/jetbrains","verify":"https://unfragile.ai/api/v1/verify?slug=jetbrains","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}