Skip to content
Back to search

mcp-steroid

Give your AI Agent a whole IDE, not just the files

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/jetbrains--mcp-steroid/badge.svg)](/listings/jetbrains--mcp-steroid)

HTML

<a href="/listings/jetbrains--mcp-steroid"><img src="/api/listings/jetbrains--mcp-steroid/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

1. Install devrig — one command

**macOS / Linux**

curl -fsSL https://devrig.dev/install.sh | sh

**Windows**

irm https://devrig.dev/install.ps1 | iex

The script does exactly two things: it installs the `devrig` CLI with its own bundled runtime into `~/.mcp-steroid`, and it registers the stable `devrig` launcher on your `PATH` (if `devrig` is not found afterwards, open a new terminal or add `~/.mcp-steroid/bin` to `PATH`). It never touches your agent configs or your IDEs — it finishes by printing the explicit next-step commands (steps 2 and 3 below). Installation is idempotent; re-run it any time to update.

2. Register your AI agent

devrig install claude
devrig install codex
devrig install gemini

`devrig install <agent>` registers devrig as the `mcp-steroid` MCP server in Claude Code, Codex, or Gemini (one of `claude`, `codex`, `gemini`). The entry lands in the user-scope config, so it is visible from every project. For any other MCP client, `devrig install config` prints the manual `mcp.json` snippet to paste. See the [devrig CLI guide](https://devrig.dev/docs/devrig/) for the full command set.

3. Install the MCP Steroid plugin

devrig install plugin

`devrig install plugin` installs (or updates) the MCP Steroid plugin into every JetBrains IDE currently running on your machine — each IDE asks for your confirmation with its own native install dialog, so nothing is installed silently. Alternatively, install **MCP Steroid** from the [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/30019-mcp-steroid) (search **MCP Steroid** in **Settings > Plugins > Marketplace**).

**Requirements**

- A JetBrains IDE — IntelliJ IDEA, PyCharm, GoLand, WebStorm, Rider, CLion, or Android Studio. - A standard desktop IDE runs with a real display: the normal GUI on macOS/Windows, or under **Xvfb** (a virtual X display) on Linux/CI. Plain non-backend headless mode is unsupported (best-effort, see [#177](https://github.com/jonnyzzz/mcp-steroid/issues/177)); a frontendless Remote Development backend is supported. Backend product mode, not the presence of a client window or the raw AWT-headless flag alone, determines that distinction — see [Running devrig in CI](https://devrig.dev/docs/running-on-ci/). - An MCP-compatible AI agent (Claude Code, Codex, or Gemini).

For a clean machine with no IDE running, an agent can discover the download catalog with `devrig backend download --json`, install IDEA Ultimate 2026.2, and call `steroid_open_project`. The managed IU-262 backend starts on demand as a frontendless Remote Development backend with MCP Steroid included; no separate start command or client window is required. Readiness is the project path plus Maven/Gradle import, not a screenshot. See the [devrig CLI guide](https://devrig.dev/docs/devrig/#frontendless-intellij-idea-ultimate-20262).

**Faster plugin updates (optional):** add `https://devrig.dev/updatePlugins.xml` in **Settings > Plugins > Gear icon > Manage Plugin Repositories...**. Or install a ZIP from [GitHub Releases](https://github.com/jonnyzzz/mcp-steroid/releases) via **Install Plugin from Disk**.

Verify the connection

When the plugin starts, it writes the connection details to `.idea/mcp-steroid.md` in each open project. Ask your agent to list the open projects:

claude -p "List all open projects using steroid_list_projects"
codex exec "List all open projects using steroid_list_projects"
gemini "List all open projects using steroid_list_projects"

If you see your open IntelliJ projects, the connection works. The plugin also serves the raw server URL at `http://127.0.0.1:6315/mcp` (Streamable HTTP transport) for clients that prefer to talk to the IDE directly.

Local development loop (deploy both halves from a checkout)

Working on MCP Steroid itself? Two Gradle tasks push your checkout into the live environment — no IDE restarts, no reinstalling.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 305 lines · 2 findings marked
  1. # MCP Steroid
  2. <p align="center">
  3. <img src="website/static/pluginIcon.svg" alt="MCP Steroid Logo" width="120" height="120">
  4. </p>
  5. <p align="center">
  6. <strong>Connect your AI coding agent to a real JetBrains IDE</strong><br>
  7. <em>Install <code>devrig</code>, and your agent works through the whole IntelliJ — not just the files</em>
  8. </p>
  9. <p align="center">
  10. <a href="https://github.com/jonnyzzz/mcp-steroid/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-Apache%202.0-blue.svg" alt="License"></a>
  11. <a href="https://plugins.jetbrains.com/plugin/30019-mcp-steroid"><img src="https://img.shields.io/badge/JetBrains-Marketplace-orange.svg" alt="JetBrains Marketplace"></a>
  12. <a href="https://discord.gg/e9qgQ7NeTC"><img src="https://img.shields.io/badge/Discord-Community-5865F2.svg" alt="Discord"></a>
  13. </p>
  14. <p align="center">
  15. <a href="https://devrig.dev">Website</a> &bull;
  16. <a href="https://www.youtube.com/playlist?list=PLitZWClhc4Qgz3w8qrtctMR_lpIc81n0f">Demo Videos</a> &bull;
  17. <a href="https://jonnyzzz.com/blog/2026/04/07/mcp-steroid-open-source/">Blog Post</a> &bull;
  18. <a href="https://discord.gg/e9qgQ7NeTC">Discord</a>
  19. </p>
  20. ---
  21. ## What is devrig?
  22. **[`devrig`](https://devrig.dev/docs/devrig/)** is the product you install: a small command-line
  23. tool that connects your AI coding agent (Claude Code, Codex, or Gemini) to a real JetBrains IDE.
  24. It brings **its own runtime**, registers itself with your agent, and bridges the agent's calls to
  25. the IDE — no manual MCP wiring.
  26. devrig reaches the IDE through **MCP Steroid**, a JetBrains IDE plugin (this repo) that exposes the
  27. IDE's real semantic actions — typed refactorings, inspections, the debugger, and test runs — over
  28. the open [Model Context Protocol](https://modelcontextprotocol.io/). You install devrig; devrig
  29. uses MCP Steroid.
  30. Unlike file-only assistants, this gives AI agents the same capabilities developers use: semantic
  31. code understanding, advanced refactorings, debugging, test running, visual awareness, and the
  32. entire IntelliJ API surface — all inside the running IDE's JVM.
  33. ### One bridge, every IDE
  34. A single `devrig` process connects your AI Agent to **all** the IntelliJ-family IDEs running on
  35. your machine at once — each open on a different project — and can download and start more on demand.
  36. <p align="center">
  37. <img src="website/static/devrig-bridge.svg" alt="One devrig bridge connects your AI Agent to all running IDEs at once — and can start more" width="720">
  38. </p>
  39. ### What your agent gets
  40. - **Visual IDE understanding** — screenshots + OCR + component tree
  41. - **UI automation** — control the IDE like a human developer
  42. - **Native IntelliJ APIs** — PSI, inspections, refactorings, and more
  43. - **Kotlin scripting** — full platform access at runtime via `steroid_execute_code`
  44. - **Standard MCP protocol** — connects to MCP-compatible AI agents
  45. We continuously measure IDE-access vs plain-shell agents on real codebases. See the
  46. [experiment findings](https://devrig.dev/docs/experiment-findings/) for the evidence-based results.
  47. ### Explore the CLI
  48. The command tree is discoverable from either direction:
  49. ```bash
  50. devrig --help
  51. devrig tools
  52. devrig help execute_code
  53. devrig list_projects --json
  54. devrig open_project --project_path="$PWD" --task_id=demo-open --reason="open current project from CLI" --wait --json
  55. devrig prompt mcp-steroid://prompt/skill --project_name="PROJECT_NAME_FROM_LIST_PROJECTS" --json
  56. ```
  57. `list_projects` is canonical (`projects` and `project` are compatibility aliases). Human output is
  58. readable and may use terminal color; commands that advertise `--json` emit one ANSI-free document for
  59. agents and scripts. Incomplete commands print focused help with every missing value. See the
  60. [devrig CLI guide](https://devrig.dev/docs/devrig/) or the contributor
  61. [CLI contract](docs/devrig-cli-contract.md).
  62. ---
  63. ## Install
  64. ### 1. Install devrig — one command
  65. **macOS / Linux**
  66. ```bash
  67. curl -fsSL https://devrig.dev/install.sh | sh
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 91 on GitHub
  68. ```
  69. **Windows**
  70. ```powershell
  71. irm https://devrig.dev/install.ps1 | iex
  72. ```
  73. The script does exactly two things: it installs the `devrig` CLI with its own bundled runtime into `~/.mcp-steroid`, and it registers the stable `devrig` launcher on your `PATH` (if `devrig` is not found afterwards, open a new terminal or add `~/.mcp-steroid/bin` to `PATH`). It never touches your agent configs or your IDEs — it finishes by printing the explicit next-step commands (steps 2 and 3 below). Installation is idempotent; re-run it any time to update.
  74. ### 2. Register your AI agent
  75. ```bash
  76. devrig install claude
  77. devrig install codex
  78. devrig install gemini
  79. ```
  80. `devrig install <agent>` registers devrig as the `mcp-steroid` MCP server in Claude Code, Codex, or Gemini (one of `claude`, `codex`, `gemini`). The entry lands in the user-scope config, so it is visible from every project. For any other MCP client, `devrig install config` prints the manual `mcp.json` snippet to paste. See the [devrig CLI guide](https://devrig.dev/docs/devrig/) for the full command set.
  81. ### 3. Install the MCP Steroid plugin
  82. ```bash
  83. devrig install plugin
  84. ```
  85. `devrig install plugin` installs (or updates) the MCP Steroid plugin into every JetBrains IDE currently running on your machine — each IDE asks for your confirmation with its own native install dialog, so nothing is installed silently. Alternatively, install **MCP Steroid** from the [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/30019-mcp-steroid) (search **MCP Steroid** in **Settings > Plugins > Marketplace**).
  86. **Requirements**
  87. - A JetBrains IDE — IntelliJ IDEA, PyCharm, GoLand, WebStorm, Rider, CLion, or Android Studio.
  88. - A standard desktop IDE runs with a real display: the normal GUI on macOS/Windows, or under **Xvfb** (a virtual X display) on Linux/CI. Plain non-backend headless mode is unsupported (best-effort, see [#177](https://github.com/jonnyzzz/mcp-steroid/issues/177)); a frontendless Remote Development backend is supported. Backend product mode, not the presence of a client window or the raw AWT-headless flag alone, determines that distinction — see [Running devrig in CI](https://devrig.dev/docs/running-on-ci/).
  89. - An MCP-compatible AI agent (Claude Code, Codex, or Gemini).
  90. For a clean machine with no IDE running, an agent can discover the download catalog with `devrig backend download --json`, install IDEA Ultimate 2026.2, and call `steroid_open_project`. The managed IU-262 backend starts on demand as a frontendless Remote Development backend with MCP Steroid included; no separate start command or client window is required. Readiness is the project path plus Maven/Gradle import, not a screenshot. See the [devrig CLI guide](https://devrig.dev/docs/devrig/#frontendless-intellij-idea-ultimate-20262).
  91. **Faster plugin updates (optional):** add `https://devrig.dev/updatePlugins.xml` in **Settings > Plugins > Gear icon > Manage Plugin Repositories...**. Or install a ZIP from [GitHub Releases](https://github.com/jonnyzzz/mcp-steroid/releases) via **Install Plugin from Disk**.
  92. ### Verify the connection
  93. When the plugin starts, it writes the connection details to `.idea/mcp-steroid.md` in each open project. Ask your agent to list the open projects:
  94. ```bash
  95. claude -p "List all open projects using steroid_list_projects"
  96. codex exec "List all open projects using steroid_list_projects"
  97. gemini "List all open projects using steroid_list_projects"
  98. ```
  99. If you see your open IntelliJ projects, the connection works. The plugin also serves the raw server URL at `http://127.0.0.1:6315/mcp` (Streamable HTTP transport) for clients that prefer to talk to the IDE directly.
  100. ### Local development loop (deploy both halves from a checkout)
  101. Working on MCP Steroid itself? Two Gradle tasks push your checkout into the live environment — no IDE restarts, no reinstalling.
  102. **One-time per IDE**: install the [Plugin Hot Reload](https://github.com/jonnyzzz/intellij-plugin-hot-reload) plugin into every IDE you deploy to — download the ZIP from its Releases page, then `Settings | Plugins | ⚙ | Install Plugin from Disk…`, restart once. It exposes the local hot-reload endpoint (a `~/.<pid>.hot-reload` marker per running IDE) that `deployPlugin` talks to.
  103. ```bash
  104. # 1. devrig (the CLI): build, stage under ~/.mcp-steroid/devrig/, and regenerate the
  105. # ~/.mcp-steroid/bin/devrig launcher via `devrig install devrig`.
  106. ./gradlew deployDevrig
  107. # assert: the launcher runs YOUR build — a dev version stamped with your checkout's git hash
  108. ~/.mcp-steroid/bin/devrig version
  109. # → <base>.19999-SNAPSHOT-<git hash of your HEAD>
  110. # 2. the IDE plugin: build the plugin ZIP and hot-reload it into every running IDE.
  111. ./gradlew :ij-plugin:deployPlugin
  112. # assert: the task output ends with SUCCESS per IDE —
  113. # Installing and loading plugin: MCP Steroid (<base>.19999-SNAPSHOT-<git hash>)
  114. # Plugin MCP Steroid reloaded successfully
  115. ```
  116. Both tasks fail loudly instead of half-deploying: `deployDevrig` fails when `devrig install devrig` cannot write the launcher (e.g. a `DEVRIG_BIN_NO_AUTO_REGISTER` opt-out), and `deployPlugin` fails with `No running IDEs found` when no IDE with the hot-reload plugin is up, or on anything but `SUCCESS` from an IDE.
  117. ---
  118. ## Compatible AI Agents
  119. `devrig install` registers MCP Steroid directly with:
  120. - **Claude** (Claude Code)
  121. - **Codex** CLI
  122. - **Gemini** CLI
  123. MCP Steroid speaks the standard Model Context Protocol, so other MCP-capable clients can also connect to the plugin's server directly — see [How it works](https://devrig.dev/docs/how-it-works/).
  124. ---
  125. ## Capabilities
  126. ### Design philosophy in one breath
  127. The MCP tool surface is **intentionally small** — power lives in
  128. `mcp-steroid://` prompt resources that teach agents to call IntelliJ's
  129. APIs directly inside `steroid_execute_code`. New tools and new
  130. `McpScriptContext` methods are not the lever for "agents deliver more";
  131. better recipes are. The full canonical statement lives in
  132. [`docs/PHILOSOPHY.md`](docs/PHILOSOPHY.md) and is mirrored at runtime
  133. as `mcp-steroid://skill/design-philosophy`.
  134. ### 8 MCP Tools
  135. | Tool | Description |
  136. |------|-------------|
  137. | **Execute Code** (`steroid_execute_code`) | Run Kotlin code inside the IDE's JVM with full API access |
  138. | **Execute Feedback** (`steroid_execute_feedback`) | Provide execution ratings back to agents |
  139. | **Fetch Resource** (`steroid_fetch_resource`) | Fetch any `mcp-steroid://` skill guide / recipe by URI |
  140. | **Vision Screenshot** (`steroid_take_screenshot`) | Capture IDE screenshots with component metadata |
  141. | **Vision Input** (`steroid_input`) | Send keyboard/mouse events to the IDE via a sequence-string DSL |
  142. | **List Projects** (`steroid_list_projects`) | Discover all open IntelliJ projects |
  143. | **List Windows** (`steroid_list_windows`) | Enumerate IDE windows and components |
  144. | **Open Project** (`steroid_open_project`) | Open projects programmatically |
  145. ### 58 MCP Resources
  146. Comprehensive guides and examples covering:
  147. - **LSP Operations** (11) — Go to definition, find references, hover, completion
  148. - **IDE Power Operations** (22) — Refactorings, code generation, project analysis
  149. - **Debugger Integration** (7) — Breakpoints, thread control, debugging workflows
  150. - **Test Runner** (10) — Run tests, inspect results, navigate test trees
  151. - **VCS Operations** (3) — Git annotations, file history
  152. - **Project Workflows** (4) — Open projects with trust levels
  153. - **Skill Guides** (3) — IntelliJ API, debugger, and test runner guides
  154. ---
  155. ## Featured Demo Videos
  156. | Video | Description | Duration |
  157. |-------|-------------|----------|
  158. | [Codex Debugs in IntelliJ IDEA](https://www.youtube.com/watch?v=HtDDNyAoLak) | Full debugging session with Codex | 1:03:24 |
  159. | [CodeDozer Demo 5](https://www.youtube.com/watch?v=6ByedA15n8Q) | Most popular demo | 1:00 |
  160. | [CodeDozer & IntelliJ Debugger](https://www.youtube.com/watch?v=8MjogrpfXLU) | Debugger integration showcase | 8:25 |
  161. | [Now we call tasks in IntelliJ](https://www.youtube.com/watch?v=JGcRk7Y3-Z8) | Task execution demo | 2:21 |
  162. | [Real Work in Monorepo Part 2](https://www.youtube.com/watch?v=ibc0saTT06M) | Deep dive into real workflow | 18:37 |
  163. | [Cursor Talks with IntelliJ](https://www.youtube.com/watch?v=QIl57FrAJtk) | Cursor integration | 0:44 |
  164. Watch all demos: [MCP Steroid Playlist](https://www.youtube.com/playlist?list=PLitZWClhc4Qgz3w8qrtctMR_lpIc81n0f)
  165. ---
  166. ## Configuration
  167. MCP Steroid can be configured via IntelliJ's Registry (`Help > Find Action > Registry`) or JVM system properties.
  168. | Registry Key | Default | Description |
  169. |--------------|---------|-------------|
  170. | `mcp.steroid.server.port` | 6315 | MCP server port (0 for auto-assign) |
  171. | `mcp.steroid.server.host` | 127.0.0.1 | Bind address (use 0.0.0.0 for Docker) |
  172. | `mcp.steroid.storage.path` | (empty) | Custom storage path (default: `~/.mcp-steroid/runs/`) |
  173. See the full [Configuration Documentation](https://devrig.dev/docs/configuration/) on the website.
  174. ---
  175. ## Architecture
  176. - **Technology:** Kotlin on the JVM, running inside the IDE process
  177. - **HTTP Server:** Ktor 3.3.2 (Streamable HTTP + SSE)
  178. - **Protocol:** Model Context Protocol (MCP)
  179. - **Default Port:** 6315
  180. - **OCR:** Tesseract 5.5.1
  181. - **Platform:** IntelliJ Platform Plugin SDK
  182. The server runs **inside the IDE's JVM process** — no inter-process communication. Direct access to the project model, semantic index, PSI tree, test runner, debugger, and VCS layer.
  183. ---
  184. ## About the Project
  185. **MCP Steroid** is an open-source project by Eugene Petrenko ([@jonnyzzz](https://linkedin.com/in/jonnyzzz)), licensed under [Apache 2.0](LICENSE).
  186. Read more:
  187. - [MCP Steroid Is Now Open Source](https://jonnyzzz.com/blog/2026/04/07/mcp-steroid-open-source/) — announcement and project history
  188. - [IntelliJ as a Skill Factory](https://jonnyzzz.com/blog/2026/04/08/mcp-steroid-skill-factory/) — build custom agent skills without plugin development
  189. - [Project Assessment: 75 Days, 1300+ Commits](https://jonnyzzz.com/blog/2026/02/23/mcp-steroid-project-assessment/) — architecture and quality deep dive
  190. *IntelliJ IDEA, IntelliJ Platform, PyCharm, WebStorm, and JetBrains are trademarks of JetBrains s.r.o.*
  191. ---
  192. ## Contributing
  193. We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on
  194. how to get started, and [CONTRIBUTORS.md](CONTRIBUTORS.md) for the list of people
  195. who have helped make MCP Steroid better.
  196. ---
  197. ## License
  198. MCP Steroid is open-source software licensed under the [Apache License 2.0](LICENSE).
  199. ---
  200. ## Links
  201. - **Website:** [devrig.dev](https://devrig.dev)
  202. - **JetBrains Marketplace:** [plugins.jetbrains.com](https://plugins.jetbrains.com/plugin/30019-mcp-steroid)
  203. - **Discord:** [discord.gg/e9qgQ7NeTC](https://discord.gg/e9qgQ7NeTC)
  204. - **GitHub Issues:** [github.com/jonnyzzz/mcp-steroid/issues](https://github.com/jonnyzzz/mcp-steroid/issues)
  205. - **GitHub Sponsors:** [github.com/sponsors/jonnyzzz](https://github.com/sponsors/jonnyzzz)
  206. - **Blog:** [jonnyzzz.com](https://jonnyzzz.com)
  207. - **YouTube:** [@jonnyzzz](https://youtube.com/@jonnyzzz)
  208. - **LinkedIn:** [jonnyzzz](https://linkedin.com/in/jonnyzzz)
  209. - **X/Twitter:** [@jonnyzzz](https://x.com/jonnyzzz)
  210. ---
  211. <p align="center">
  212. <sub>Built with care for the AI agent developer community</sub>
  213. </p>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.