v0.101

devrig is the recommended entry point. Direct use of the MCP Steroid plugin's HTTP server is still fully supported, but we recommend migrating to devrig: it owns installation, the Java runtime, agent registration, and backend lifecycle.

Independent project. MCP Steroid / Devrig is an independent open-source project. It is not affiliated with, sponsored by, or endorsed by JetBrains.

Release Date: June 24, 2026

Highlights

One-command install

You no longer assemble devrig by hand. A generated bootstrap installer does it for you:

# macOS / Linux
curl -fsSL https://mcp-steroid.jonnyzzz.com/install.sh | sh

# Windows
irm https://mcp-steroid.jonnyzzz.com/install.ps1 | iex

The installer detects your platform and downloads the matching devrig build and a Java 25 runtime (Amazon Corretto 25 on macOS/Linux/Windows-x64; Azul Zulu 25 on Windows-arm64) — so you no longer need to install a JDK yourself. Every URL and SHA-256 is baked in at build time (no live discovery), each download is SHA-256–verified, and a missing prerequisite is reported up front rather than failing half-way. It then hands off to devrig install devrig, which registers the stable launcher.

A predictable layout under ~/.mcp-steroid

devrig keeps everything under one fixed home — bin/devrig (the stable launcher on your PATH, owned and self-healed by the binary on every start) and binaries/<artifact>-<os>-<cpu>-<version>-<sha12>/ (the content-addressed devrig dist + the matching Java 25). Re-installs are idempotent, and the launcher pins the Java 25 it runs under.

devrig install is smoother

• devrig install <claude | codex | gemini> is now idempotent — re-running upgrades an existing registration in place and consolidates stray entries into one (#83, #84).
• devrig install <agent> --check is a read-only doctor that reports registration status without changing anything (#86).
• devrig mcp is now the canonical stdio subcommand (mpc stays as a hidden alias) (#85).

Smarter backends — start what’s installed

devrig now reasons about backends as four groups (running-compatible, running-incompatible, startable, downloadable). steroid_open_project can start a stopped-but-installed backend for you, re-provision the current plugin, and wait until it’s reachable — no manual launch. backend_name routing targets a specific backend when several run (#87); list_projects / list_windows no longer mislabel the backend or duplicate their payload and report installed plugins as a structured plugins[] section (#88, #89, #90); and project_name is now an opaque <name>-<hash> routing key so same-named projects route correctly (#92).

A devrig-first settings page

The plugin’s Tools → MCP Steroid settings page is back and reworked around agents and devrig (#80, #103): copyable per-OS install one-liners up top, the actual server port (not a hard-coded one), a fit-to-paste JSON config, and the legacy raw-HTTP path flagged as non-recommended with a link to the devrig docs.

steroid_execute_code quality-of-life

The most-used PSI subpackages are imported by default so common recipes need fewer import lines (#42), and steroid_take_screenshot now reports coordinates in true pixel space so steroid_input clicks land where you expect (#55). The IDE recipe corpus is now genuinely multi-IDE — articles that were accidentally IntelliJ-only now resolve in PyCharm and the rest (#81, #98).

Download

Custom Plugin Repository (Recommended)

Add this URL in Settings -> Plugins -> ⚙️ -> Manage Plugin Repositories…:

https://mcp-steroid.jonnyzzz.com/updatePlugins.xml

The IDE will find the plugin and notify you when updates are available.

JetBrains Marketplace

Search for MCP Steroid in Settings -> Plugins -> Marketplace.

Manual Download

• Download the plugin ZIP from the release page
• Download the devrig CLI ZIP from the same release page
• Release page on GitHub

1. Download the plugin .zip from the GitHub release page above
2. In IntelliJ IDEA, go to Settings -> Plugins -> ⚙️ -> Install Plugin from Disk…
3. Select the downloaded ZIP file
4. Restart the IDE

End User License Agreement (EULA) - By downloading and using this plugin, you agree to the terms of the EULA.

Connecting to Cloud Agents

See Getting Started.

Supported AI Agents

Claude Code, Codex, Gemini, Cursor, and any other coding agent that supports the latest MCP via HTTP Streaming — or, with devrig, over stdio.

Reporting issues

Use “Collect Logs and Diagnostics Data” action in IntelliJ to collect information about the problem. Review the log file for specific problem.

Discord Community

Message Eugene on LinkedIn for a Discord invite: linkedin.com/in/jonnyzzz

Direct invite link: discord.gg/e9qgQ7NeTC

That is the best place to discuss the plugin, ideas, features.

Feedback

We’re actively learning what content and features work best. Your feedback is invaluable!

If you encounter any issues or have suggestions, please let us know in GitHub Issues! Your feedback directly shapes the development of MCP Steroid.

Fixed Issues

• #96, #97 — devrig installation is now the main website content, with a one-command bootstrap installer.
• #83, #84 — devrig install <agent> works reliably and is idempotent.
• #86 — clearer / self-healing MCP installation state, plus install <agent> --check.
• #85 — devrig mcp added as the canonical subcommand (alias of mpc).
• #80, #103 — the Tools → MCP Steroid settings page is back, devrig-first, showing the actual server port.
• #87 — backend_name routing parameter for steroid_open_project.
• #88 — installed plugins modeled as a plugins[] section per backend.
• #89, #90 — list_projects / list_windows no longer mislabel the backend or duplicate their payload.
• #92 — steroid_execute_code routes correctly when two projects share a folder name (opaque project_name).
• #42 — default imports for the most-used PSI subpackages.
• #55 — steroid_take_screenshot reports true pixel-space coordinates.
• #81, #98 — IDE recipe corpus is genuinely multi-IDE (e.g. ide/inspect-and-fix now resolves in PyCharm).
• #95 — a “refresh-then-find” idiom so scripts pick up files created outside the IDE.
• #62, #70 — recipes warn about headless popup-action no-ops and ActionGroup.getChildren(null).

Known issue: #78 — on a Windows-side IDE opening a WSL-hosted project, set the mcp.steroid.storage.path registry key to a native Windows path as a workaround.

Known issue: #150 — on Windows, devrig start/install can hang during user-PATH registration (the PowerShell helper is spawned with an open stdin). Workaround: create the marker file %USERPROFILE%\.mcp-steroid\bin\.user-path-registered (any content) so devrig skips that step, then add %USERPROFILE%\.mcp-steroid\bin to your PATH manually (agents use the absolute launcher path, so MCP works regardless). A fix is in progress. Kudos to Serge for reporting it.

Acknowledgements

Thanks to @andrii0lomakin for the steroid_execute_code default-imports request (#42), and to @ivanpajic for reporting and patiently helping chase down the plugin install/discovery problems on recent IntelliJ builds (#79).