JetBrains MCP Proxy Server

Created By
JetBrainsa year ago
A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio
Overview

What is Mcp Jetbrains?

Mcp Jetbrains is a proxy server that allows clients to communicate with JetBrains IDEs seamlessly, enhancing the interaction between AI tools and IDE applications.

How to use Mcp Jetbrains?

To use Mcp Jetbrains, install the MCP Server plugin from the JetBrains plugins marketplace and configure it within the Claude Desktop application by modifying the 'claude_desktop_config.json' file to include the server commands and arguments.

Key features of Mcp Jetbrains?

  • Proxies requests from client applications to JetBrains IDE.
  • Compatible with Claude Desktop for enhanced AI interactions.
  • Allows configuration for multiple IDE instances.

Use cases of Mcp Jetbrains?

  1. Enabling AI chatbots to assist developers directly within JetBrains IDEs.
  2. Streamlining workflows by integrating AI tools with IDE functionalities.
  3. Enhancing coding assistance features through real-time feedback.

FAQ from Mcp Jetbrains?

  • How do I install the MCP Server plugin?

You can install the MCP Server plugin from the JetBrains plugins repository here.

  • What configuration is needed for Claude Desktop?

You need to add specific JSON configuration in 'claude_desktop_config.json' to setup the MCP server with command and environment variables.

  • Is Mcp Jetbrains compatible with all JetBrains IDEs?

Yes! Mcp Jetbrains can be used with multiple JetBrains IDEs as long as they are properly configured.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JetBrains
Star
730
Language
JavaScript
License
Apache-2.0 license
Category
ai-chatbot

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago