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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago