JetBrains IDE MCP Server
by a-penguin3
README.md
# dsh-jetbrains-mcp
**JetBrains IDE MCP Server for [DeepSeek Harness](https://github.com/sandbaseai/deepseek-harness-handbook)** — the IDE's own build, refactoring, debugger, database and Git tools, in the agent's tool list.
English | [中文](README.zh.md)

## What it gives the agent
Once installed and enabled, the model sees IntelliJ IDEA's MCP tools under a stable namespace:
| Group | Tools |
| --- | --- |
| Build & run | `build_project`, `get_run_configurations`, `execute_run_configuration` |
| Code understanding | `search_symbol`, `search_text`, `search_regex`, `search_file`, `get_symbol_info`, `analyze_calls`, `generate_psi_tree`, `list_directory_tree`, `read_file` |
| Quality | `get_file_problems`, `lint_files`, `reformat_file`, `generate_inspection_kts_api`, `generate_inspection_kts_examples`, `run_inspection_kts` |
| Editing | `create_new_file`, `apply_patch`, `open_file_in_editor`, `rename_refactoring` |
| Debugger | the `xdebug_*` family — breakpoints, stepping, stacks, frame values, expression evaluation, variable mutation |
| Database | `list_database_connections`, `execute_sql_query`, `preview_table_data`, `introspect_schema`, `list_schema_objects`, … |
| VCS | `git_status`, `get_repositories` |
| Terminal | `execute_terminal_command` |
Names are `mcp__jetbrains__<tool>`, the same shape Claude Code and Codex use, so a tool reference in chat history or a permission rule keeps working across restarts.
Plus one tool of its own: **`jetbrains_mcp_doctor`**, which explains what is wrong when the `mcp__jetbrains__*` tools are missing.
## Requirements
- **IntelliJ IDEA, PyCharm, WebStorm, DataGrip or any other JetBrains IDE, 2025.2 or newer** (any JetBrains IDE that bundles the **MCP Server** plugin) with **Settings | Tools | MCP Server → Enable MCP Server** switched on. The IDE may use any port; this bundle discovers it.
- **DeepSeek Harness 0.2.0 or newer** with the in-box `@deepseek-ai/dsh-mcp-client` bridge (DSH Desktop, or `dsh web`).
- No Node.js on `PATH` is required: the adapter runs on the host's own runtime.
## Install
**From the plugin market (recommended).** Open **Plugins → Discover** in DSH, search for `dsh-jetbrains-mcp`, and install it.
**From a terminal.**
```sh
dsh plugin --profile <profile> add dsh-jetbrains-mcp
```
Replace `<profile>` with the profile your host uses (`desktop` for DSH Desktop's own profile is managed by the app — install through **Settings → Plugins** there). Restart the host afterwards.
**From a checkout of this package.**
```sh
dsh plugin --profile <profile> add /absolute/path/to/dsh-jetbrains-mcp
```
## Usage
Most IDE tools take a **`projectPath`** argument — the directory opened in the IDE:
```text
use mcp__jetbrains__build_project with projectPath "F:/work/my-service"
```
Without it the IDE answers *"Unable to determine the target project"*: the MCP server is IDE-wide, so the project is not implied by the connection. Everything else behaves like any other tool.
## How it works
```text
DSH agent
└─ tool call mcp__jetbrains__build_project
└─ @deepseek-ai/dsh-mcp-client (in-box, mounted by this bundle's patch row)
└─ bin/jetbrains-mcp-bridge.mjs (this package, zero dependencies)
│ stdio ⇄ HTTP+SSE
└─ IntelliJ IDEA MCP Server http://127.0.0.1:<port>/sse
```
JetBrains IDEs' MCP Server exposes the **legacy HTTP+SSE** transport (`GET /sse`, then `POST /message?sessionId=…`), while DSH's in-box MCP client speaks **stdio** or **streamable-http**. The adapter in `bin/` is the missing half: a stdio MCP server for DSH and an SSE MCP client for the IDE. It is a few hundred lines of Node built-ins — no SDK copy, no second protocol implementation beyond this translation.
The IDE's port is read from `%APPDATA%\JetBrains\*\options\mcpServer.xml` (fallback `64342`) on every launch, so changing the port inside the IDE needs no edit here.
Row paths are computed by the Loader at mount time (`!!js` expressions over the entry's own context), so nothing is written into your profile configuration and no absolute path is baked into the package.
### Overrides
For debugging only; set them in the environment the host runs in:
| Variable | Effect |
| --- | --- |
| `DSH_JETBRAINS_MCP_URL` | Full SSE URL, e.g. `http://127.0.0.1:64342/sse` |
| `DSH_JETBRAINS_MCP_NODE` | Node executable to run the adapter |
| `DSH_JETBRAINS_MCP_ADAPTER` | Absolute path of the adapter script |
## Troubleshooting
Start with **`jetbrains_mcp_doctor`** — it reports the adapter path it found, the command the bridge row runs, every JetBrains product that has MCP settings and on which port, a live probe of that endpoint, and the registered `mcp__jetbrains__*` tools.
| Symptom | Cause |
| --- | --- |
| No `mcp__jetbrains__*` tool at all | The row `dsh-jetbrains-mcp-bridge` is off, or the host needs a restart after installation |
| `jetbrains_mcp_doctor` says *NONE FOUND* | No IDE settings — the MCP Server plugin is not installed/enabled, or no JetBrains IDE has run on this account |
| Probe reports a timeout or an error | The IDE is closed, or its MCP server is disabled in **Settings → Tools → MCP Server** |
| Tools exist but every call answers *"Unable to determine the target project"* | Pass `projectPath` |
| Tools disappear when the IDE closes | Expected: the session dies with the IDE and the row reconnects on its own when it is back |
## Security
- The adapter connects to `127.0.0.1` only.
- The IDE's **Brave Mode** (`enableBraveMode`, on by default in some versions) makes the IDE execute MCP tool calls **without asking again in the IDE**. If you do not want that, turn Brave Mode off in the IDE's MCP settings; the agent's own approval flow still applies on the DSH side.
- Installing this plugin means an agent with tool access can build, run, refactor, debug and run SQL through your IDE. Treat it like handing over the IDE.
## License
MIT — see [LICENSE](LICENSE).
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues