Skip to main content
mcpSource-backed

JetBrains MCP Server for Claude

Official built-in JetBrains MCP server that connects Claude and other MCP clients to IntelliJ IDEA, PyCharm, WebStorm, Android Studio, and other IntelliJ-based IDEs for project analysis, code insight, file edits, build feedback, run configurations, terminal commands, debugger context, and optional database tools.

by JetBrains · submitted by oktofeesh1·added 2026-06-04·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://www.jetbrains.com/help/idea/mcp-server.html, https://github.com/JetBrains/mcp-jetbrains
Safety notes
JetBrains MCP is built into IntelliJ-based IDEs starting with 2025.2. The `JetBrains/mcp-jetbrains` npm proxy repository is deprecated, so prefer the IDE's current Settings | Tools | MCP Server workflow and use the npm proxy only as a compatibility bridge when needed., The MCP server exposes IDE tools that can analyze code, modify files, build projects, run configurations, execute terminal commands, inspect debugger sessions, and access optional database tooling depending on the enabled plugins and exposed tool list., Keep the server bound to local clients unless external access is explicitly required. Enabling external IDE connections and setting a LAN host can make the IDE's MCP surface reachable from Docker containers or other machines on the network., Do not enable command execution without confirmation for sensitive repositories, production credentials, deploy-capable projects, or untrusted prompt workflows. Treat JetBrains' brave mode as a privileged automation setting., Disable exposed tools that are not needed for the current workflow, especially terminal, run configuration, debugger, and database tools in shared or production-like environments., Database tools should use read-only database users when the assistant only needs schema discovery, query inspection, or sample data. Do not rely on prompts as the only guardrail against write queries.
Privacy notes
Tool results can expose project paths, source code, open files, selected text, dependency names, compiler diagnostics, inspections, symbol metadata, run configuration names, terminal output, stack frames, local variables, evaluated expressions, database connection names, schemas, SQL text, and query results., IDE projects often contain secrets in environment files, run configurations, test fixtures, logs, shell history, database consoles, and generated output. Exclude or redact those files before asking an assistant to inspect broad project context., MCP client transcripts, JetBrains logs, proxy logs, terminal output, and debug traces may retain file paths, code snippets, command arguments, query output, and operational details outside the IDE., If external client or Docker access is enabled, network metadata and project content can cross the local IDE boundary. Use private networks, host firewalls, narrow ports, and per-project review before exposing the server beyond localhost.
Author
JetBrains
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-04

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup. Includes a review or approval gate.

0/6 ready
Install & runtime1Configuration1Network & hosting1Review & approval1General210 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access.

5 areas
  • SafetyGeneralJetBrains MCP is built into IntelliJ-based IDEs starting with 2025.2. The `JetBrains/mcp-jetbrains` npm proxy repository is deprecated, so prefer the IDE's current Settings | Tools | MCP Server workflow and use the npm proxy only as a compatibility bridge when needed.
  • SafetyCredentials & tokensThe MCP server exposes IDE tools that can analyze code, modify files, build projects, run configurations, execute terminal commands, inspect debugger sessions, and access optional database tooling depending on the enabled plugins and exposed tool list.
  • SafetyNetwork accessKeep the server bound to local clients unless external access is explicitly required. Enabling external IDE connections and setting a LAN host can make the IDE's MCP surface reachable from Docker containers or other machines on the network.
  • SafetyCredentials & tokensDo not enable command execution without confirmation for sensitive repositories, production credentials, deploy-capable projects, or untrusted prompt workflows. Treat JetBrains' brave mode as a privileged automation setting.
  • SafetyExecution & processesDisable exposed tools that are not needed for the current workflow, especially terminal, run configuration, debugger, and database tools in shared or production-like environments.
  • SafetyGeneralDatabase tools should use read-only database users when the assistant only needs schema discovery, query inspection, or sample data. Do not rely on prompts as the only guardrail against write queries.
  • PrivacyLocal filesTool results can expose project paths, source code, open files, selected text, dependency names, compiler diagnostics, inspections, symbol metadata, run configuration names, terminal output, stack frames, local variables, evaluated expressions, database connection names, schemas, SQL text, and query results.
  • PrivacyCredentials & tokensIDE projects often contain secrets in environment files, run configurations, test fixtures, logs, shell history, database consoles, and generated output. Exclude or redact those files before asking an assistant to inspect broad project context.
  • PrivacyLocal filesMCP client transcripts, JetBrains logs, proxy logs, terminal output, and debug traces may retain file paths, code snippets, command arguments, query output, and operational details outside the IDE.
  • PrivacyNetwork accessIf external client or Docker access is enabled, network metadata and project content can cross the local IDE boundary. Use private networks, host firewalls, narrow ports, and per-project review before exposing the server beyond localhost.

Safety notes

  • JetBrains MCP is built into IntelliJ-based IDEs starting with 2025.2. The `JetBrains/mcp-jetbrains` npm proxy repository is deprecated, so prefer the IDE's current Settings | Tools | MCP Server workflow and use the npm proxy only as a compatibility bridge when needed.
  • The MCP server exposes IDE tools that can analyze code, modify files, build projects, run configurations, execute terminal commands, inspect debugger sessions, and access optional database tooling depending on the enabled plugins and exposed tool list.
  • Keep the server bound to local clients unless external access is explicitly required. Enabling external IDE connections and setting a LAN host can make the IDE's MCP surface reachable from Docker containers or other machines on the network.
  • Do not enable command execution without confirmation for sensitive repositories, production credentials, deploy-capable projects, or untrusted prompt workflows. Treat JetBrains' brave mode as a privileged automation setting.
  • Disable exposed tools that are not needed for the current workflow, especially terminal, run configuration, debugger, and database tools in shared or production-like environments.
  • Database tools should use read-only database users when the assistant only needs schema discovery, query inspection, or sample data. Do not rely on prompts as the only guardrail against write queries.

Privacy notes

  • Tool results can expose project paths, source code, open files, selected text, dependency names, compiler diagnostics, inspections, symbol metadata, run configuration names, terminal output, stack frames, local variables, evaluated expressions, database connection names, schemas, SQL text, and query results.
  • IDE projects often contain secrets in environment files, run configurations, test fixtures, logs, shell history, database consoles, and generated output. Exclude or redact those files before asking an assistant to inspect broad project context.
  • MCP client transcripts, JetBrains logs, proxy logs, terminal output, and debug traces may retain file paths, code snippets, command arguments, query output, and operational details outside the IDE.
  • If external client or Docker access is enabled, network metadata and project content can cross the local IDE boundary. Use private networks, host firewalls, narrow ports, and per-project review before exposing the server beyond localhost.

Prerequisites

  • JetBrains IDE 2025.2 or later with the bundled MCP Server plugin enabled, such as IntelliJ IDEA, PyCharm, WebStorm, or Android Studio.
  • MCP-capable client such as Claude Desktop, Claude Code, Cursor, Codex, VS Code, Windsurf, or another client that can use SSE, stdio, or HTTP Stream configuration.
  • Open JetBrains project that Claude is allowed to inspect, edit, build, run, or debug.
  • Node.js 18 or later only when using the legacy `@jetbrains/mcp-proxy` stdio bridge for older client setups.
  • Decision on which exposed tools should remain enabled for analysis, code insight, file modification, terminal commands, run configurations, debugger access, and database operations.
  • Review process before enabling command execution without confirmation or exposing the IDE to external clients, Docker containers, or non-local hosts.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Full copyable content
{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": ["-y", "@jetbrains/mcp-proxy"]
    }
  }
}

About this resource

Content

JetBrains MCP Server lets Claude and other MCP-capable clients work with an open JetBrains IDE project through the IDE itself. Starting with JetBrains IDE version 2025.2, the MCP Server plugin is bundled into IntelliJ-based IDEs and can be enabled from Settings | Tools | MCP Server. The older @jetbrains/mcp-proxy package remains useful as a stdio compatibility bridge, but JetBrains now points users to the built-in IDE workflow as the primary setup path.

This is most useful when Claude needs project-aware IDE context rather than plain filesystem access. The server can expose tools for inspections, build feedback, symbol lookup, file edits, run configurations, terminal commands, debugger sessions, and database tools depending on the IDE, installed plugins, and the user's exposed-tool settings.

Features

  • Official JetBrains MCP support bundled into IntelliJ-based IDEs starting with version 2025.2.
  • Client auto-configuration for Claude Desktop, Claude Code, Cursor, Codex, VS Code, Windsurf, and other supported clients from the IDE settings screen.
  • Manual client configuration for SSE, stdio, and HTTP Stream transports.
  • Project analysis tools for builds, file problems, dependencies, modules, and IDE inspections.
  • Code insight tools for symbol information, code navigation, and project-aware context.
  • File and editing tools for modifying project files through the open IDE.
  • Run configuration and terminal tools for supervised execution workflows.
  • Debugger toolset support for stepping, stack inspection, frame values, expression evaluation, breakpoints, and runtime state when the debugger plugin is available.
  • Optional database tools through JetBrains database plugins, including connection inspection, schema metadata, recent queries, table previews, and SQL execution.
  • Per-tool exposure controls under Settings | Tools | MCP Server | Exposed Tools.
  • Optional command execution without confirmation for trusted local workflows that intentionally need unattended runs.

Use Cases

  • Ask Claude to inspect IDE diagnostics before making a code change.
  • Build a project or compile selected files after edits and return the IDE's error and warning output.
  • Navigate symbols, dependencies, modules, and project structure without flattening the task into shell-only file search.
  • Apply small project edits through an IDE-aware workflow, then re-run build or inspection tools.
  • Debug a failing test by combining breakpoints, stack frames, local variables, and expression evaluation with Claude's reasoning.
  • Review database schemas or sample rows from a JetBrains data source using a restricted database user.
  • Keep a Claude Desktop, Claude Code, Cursor, Codex, or VS Code workflow connected to the same project state already open in IntelliJ IDEA, PyCharm, WebStorm, or Android Studio.

Installation

Built-in IDE setup

Use the built-in MCP Server plugin in a JetBrains IDE 2025.2 or later:

  1. Open the target project in the JetBrains IDE.
  2. Go to Settings | Tools | MCP Server.
  3. Click Enable MCP Server.
  4. Use Auto-Configure for supported clients, or copy the SSE, stdio, or HTTP Stream configuration manually.
  5. Restart the MCP client so the new configuration is loaded.

Legacy stdio bridge

For clients that need a stdio command, JetBrains' older proxy package can still bridge the client to the local IDE:

{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": ["-y", "@jetbrains/mcp-proxy"]
    }
  }
}

When multiple IDEs are running, set the IDE port explicitly:

{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": ["-y", "@jetbrains/mcp-proxy"],
      "env": {
        "IDE_PORT": "63342",
        "HOST": "127.0.0.1"
      }
    }
  }
}

Only configure a non-local host when you have intentionally enabled external IDE connections and reviewed the network exposure.

Source Notes

  • JetBrains documents the MCP Server as bundled into IntelliJ IDEA 2025.2 and later, with setup under Settings | Tools | MCP Server.
  • JetBrains documents automatic setup for Claude Desktop, Claude Code, Cursor, Codex, VS Code, and Windsurf, plus manual SSE, stdio, and HTTP Stream configuration.
  • The JetBrains/mcp-jetbrains repository is an official JetBrains project but is deprecated because the core functionality moved into the IDE.
  • The deprecated proxy repository remains relevant for historical stdio examples and @jetbrains/mcp-proxy compatibility notes.

Duplicate Check

Before drafting this entry, the current upstream content tree and live open PRs were checked for JetBrains, IntelliJ MCP, mcp-jetbrains, @jetbrains/mcp-proxy, the JetBrains MCP docs URL, and the official repository URL. No existing content entry or open PR covered this JetBrains MCP server.

Editorial Disclosure

Submitted as a community content entry by oktofeesh1. This listing is based on JetBrains' official documentation and official repository metadata, with no paid placement or affiliate relationship.

Source citations

Add this badge to your README

Show that JetBrains MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/jetbrains-mcp-server.svg)](https://heyclau.de/entry/mcp/jetbrains-mcp-server)

How it compares

JetBrains MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Official built-in JetBrains MCP server that connects Claude and other MCP clients to IntelliJ IDEA, PyCharm, WebStorm, Android Studio, and other IntelliJ-based IDEs for project analysis, code insight, file edits, build feedback, run configurations, terminal commands, debugger context, and optional database tools.

Open dossier

Apache-licensed Ghidra MCP bridge with GUI and headless workflows for binary analysis, decompilation, scripting, debugger access, batch operations, and Ghidra Server collaboration.

Open dossier

MCP transport bridge that converts between stdio, SSE, and Streamable HTTP so local MCP clients can reach remote servers, or remote clients can reach local stdio servers.

Open dossier

Source-install MCP server for controlling Ableton Live from Claude, including session inspection, track and clip creation, MIDI note editing, tempo and transport control, browser item loading, arrangement workflows, device parameters, automation, external plugins, audio imports, and optional ElevenLabs.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorJetBrainsbethingtonSergey Parfenyukuisato
Added2026-06-042026-06-052026-06-062026-06-06
Platforms
Harness
Source repo
Safety notesJetBrains MCP is built into IntelliJ-based IDEs starting with 2025.2. The `JetBrains/mcp-jetbrains` npm proxy repository is deprecated, so prefer the IDE's current Settings | Tools | MCP Server workflow and use the npm proxy only as a compatibility bridge when needed. The MCP server exposes IDE tools that can analyze code, modify files, build projects, run configurations, execute terminal commands, inspect debugger sessions, and access optional database tooling depending on the enabled plugins and exposed tool list. Keep the server bound to local clients unless external access is explicitly required. Enabling external IDE connections and setting a LAN host can make the IDE's MCP surface reachable from Docker containers or other machines on the network. Do not enable command execution without confirmation for sensitive repositories, production credentials, deploy-capable projects, or untrusted prompt workflows. Treat JetBrains' brave mode as a privileged automation setting. Disable exposed tools that are not needed for the current workflow, especially terminal, run configuration, debugger, and database tools in shared or production-like environments. Database tools should use read-only database users when the assistant only needs schema discovery, query inspection, or sample data. Do not rely on prompts as the only guardrail against write queries.Use this server only for binaries and systems you are authorized to inspect, debug, emulate, modify, document, or reverse engineer. The tool surface includes write-capable operations such as renaming, typing, commenting, label changes, script execution, structure creation, and project/version-control workflows. Unknown binaries, malware samples, debugger targets, and imported scripts can be dangerous; isolate analysis environments and avoid running untrusted code on a primary workstation. Headless, Docker, CI, and Ghidra Server workflows can affect shared repositories or automated pipelines if configured with write access. Keep human review on operations that change analysis state, scripts, project metadata, or shared Ghidra Server content.mcp-proxy can expose local stdio MCP servers as network services; keep the host bound to `127.0.0.1` unless remote access is intentional. Passing `--host=0.0.0.0`, permissive CORS, or named-server routes can make tools reachable by other systems on the network. Proxy configuration can include bearer tokens, OAuth client secrets, headers, server commands, environment variables, and working directories. The proxy can spawn arbitrary configured MCP server commands; only use trusted command strings and config files. Remote SSE or Streamable HTTP servers should be authenticated and trusted before forwarding client requests or tool outputs.Ableton MCP Extended can create, rename, delete, arm, mute, solo, pan, and adjust tracks; create clips; add and delete MIDI notes; set tempo; start and stop playback; fire and stop clips; and manipulate arrangement content. Device and plugin tools can load instruments or effects, enable or disable devices, delete devices, navigate presets, and change normalized parameters that may affect volume, routing, feedback, CPU load, or project sound. Automation, cue point, loop, view, browser, sample import, and arrangement controls can make broad session changes that should be reviewed before saving. The Ableton Remote Script runs a local TCP socket server inside Live; keep it available only to trusted local clients and close Ableton or remove the control surface when finished. Voice generation and audio import workflows can create new audio files and may incur third-party API costs or licensing restrictions.
Privacy notesTool results can expose project paths, source code, open files, selected text, dependency names, compiler diagnostics, inspections, symbol metadata, run configuration names, terminal output, stack frames, local variables, evaluated expressions, database connection names, schemas, SQL text, and query results. IDE projects often contain secrets in environment files, run configurations, test fixtures, logs, shell history, database consoles, and generated output. Exclude or redact those files before asking an assistant to inspect broad project context. MCP client transcripts, JetBrains logs, proxy logs, terminal output, and debug traces may retain file paths, code snippets, command arguments, query output, and operational details outside the IDE. If external client or Docker access is enabled, network metadata and project content can cross the local IDE boundary. Use private networks, host firewalls, narrow ports, and per-project review before exposing the server beyond localhost.Tool calls may expose binary names, file paths, hashes, strings, imports, exports, symbols, decompiled code, comments, type names, project names, repository URLs, debugger state, memory reads, and trace metadata. Reverse engineering projects often contain proprietary firmware, customer binaries, vulnerability findings, credentials embedded in samples, exploit indicators, and private research notes. MCP client logs, model transcripts, Ghidra project history, Docker volumes, CI logs, and Ghidra Server repositories may retain sensitive analysis data. Do not commit private binaries, generated Ghidra projects, debugger traces, analysis exports, credentials, proprietary symbols, or customer-specific reverse engineering notes.MCP requests, responses, tool outputs, progress events, headers, OAuth tokens, API access tokens, and session identifiers may pass through the proxy process. Named server config files can contain command arguments, environment variables, and credentials for downstream MCP servers. Exposed network endpoints can reveal tool names, server status, and results to clients that can reach the proxy. Logs and troubleshooting output may include endpoint URLs, command names, headers, connection errors, or server names. Store config files outside shared repositories when they include tokens or private server details.Live Set names, track names, clip names, MIDI notes, device names, plugin lists, browser paths, sample paths, cue points, arrangement details, and generated audio prompts can be sent to the MCP client and model. Optional ElevenLabs use can send voice prompts, generated-speech requests, and account metadata to a third-party API. Local logs, model transcripts, imported audio files, and configured output directories can reveal unreleased music, client work, sample libraries, voice concepts, or performance plans. Keep API keys scoped and out of committed MCP config, screenshots, issue comments, and shared prompt transcripts.
Prerequisites
  • JetBrains IDE 2025.2 or later with the bundled MCP Server plugin enabled, such as IntelliJ IDEA, PyCharm, WebStorm, or Android Studio.
  • MCP-capable client such as Claude Desktop, Claude Code, Cursor, Codex, VS Code, Windsurf, or another client that can use SSE, stdio, or HTTP Stream configuration.
  • Open JetBrains project that Claude is allowed to inspect, edit, build, run, or debug.
  • Node.js 18 or later only when using the legacy `@jetbrains/mcp-proxy` stdio bridge for older client setups.
  • Ghidra 12.1 or a compatible version installed and available on the local machine or analysis host.
  • Java 21, Maven 3.9 or newer, Python 3.10 or newer, and Python package installation available.
  • Ghidra extension deployment permissions for the user profile or headless environment.
  • Authorization to analyze the binaries, firmware, traces, symbols, and shared Ghidra projects loaded into the tool.
  • Python 3.10 or newer.
  • uv, pipx, or Docker for installation.
  • A known MCP endpoint or local stdio MCP server to bridge.
  • Review of required headers, OAuth client credentials, CORS origins, host, port, and named-server configuration.
  • Ableton Live 11 or newer.
  • Python 3.10 or newer and pip for the source-install MCP server.
  • Git for cloning the source repository.
  • The AbletonMCP Remote Script copied into Ableton Live's User Remote Scripts directory and selected as a control surface.
Install
Enable MCP Server from Settings | Tools | MCP Server in a JetBrains IDE 2025.2 or later
git clone https://github.com/bethington/ghidra-mcp.git && cd ghidra-mcp && python -m tools.setup preflight --ghidra-path GHIDRA_INSTALL_DIR
uv tool install mcp-proxy
git clone https://github.com/uisato/ableton-mcp-extended.git && cd ableton-mcp-extended && pip install -e .
Config
{
  "mcpServers": {
    "jetbrains": {
      "command": "npx",
      "args": ["-y", "@jetbrains/mcp-proxy"],
      "env": {
        "IDE_PORT": "63342",
        "HOST": "127.0.0.1"
      }
    }
  }
}
Manual-only setup:
python -m tools.setup preflight --ghidra-path GHIDRA_INSTALL_DIR
python -m tools.setup ensure-prereqs --ghidra-path GHIDRA_INSTALL_DIR
python -m tools.setup build
python -m tools.setup deploy --ghidra-path GHIDRA_INSTALL_DIR
Manual-only setup:
mcp-proxy https://example.com/sse
{
  "mcpServers": {
    "AbletonMCP": {
      "command": "python",
      "args": ["<path-to-ableton-mcp-extended/MCP_Server/server.py>"],
      "env": {
        "ELEVENLABS_API_KEY": "",
        "ELEVENLABS_OUTPUT_DIR": "<approved-ableton-audio-output-directory>"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.