Repository navigation
v0.100
Archived binary mirror of jonnyzzz/mcp-steroid v0.100.
Original publication: 2026-06-01T23:21:40Z.
Upstream tag commit: 409f23a20aa1bf21b78bd27c3a172b7962c8f0f2.
Assets retain their original filenames and bytes, verified against the upstream GitHub SHA-256 digests. The original license/EULA assets accompany each release where present. This repository hosts the static website and the binary archive.
0.100
This is a landmark release. MCP Steroid is beginning its move toward Devrig, and the
headline is a brand-new command-line tool — devrig — that becomes the foundation for where
this project is going. Try it, share what you think.
Independent project. MCP Steroid / Devrig is an independent open-source project. It is
not affiliated with, sponsored by, or endorsed by JetBrains.
Meet devrig — a CLI that gives your agent a whole IDE
devrig is a new standalone command-line tool that gives Claude Code, Codex, Gemini, and
other MCP-capable coding agents a CLI and stdio MCP bridge into a real IntelliJ-family IDE. It can
connect to an IDE you already have open, or it can download, prepare, start, and stop a managed IDE backend
itself: fetch an IntelliJ distribution (e.g., IDEA Community, Android Studio, PyCharm, IntelliJ Ultimate),
install the MCP Steroid plugin into it, and run it, so your agent gets a working IDE with no manual setup.
The first CLI surface is intentionally practical:
devrig mpc— run the stdio MCP server (this is what your agent talks to).devrig backend download | start | stop | provision— manage IDE backends.devrig install <claude | codex | gemini>— register the devrig MCP server with an agent
using the correct per-agent syntax, so thesteroid_*tools appear immediately.devrig project,devrig version,devrig help— the usual operator checks.- let us know which commands to add — the usual feedback request.
devrig keeps its state under a fixed ~/.mcp-steroid home. It ships without a bundled
runtime and is compiled for Java 25, so the agent host must provide a JDK/JRE 25+ —
on PATH, via JAVA_HOME, or via the DEVRIG_JAVA_HOME launcher override (which points only
devrig's own process at a Java 25). Install
Amazon Corretto 25
or any other JDK to run devrig.
devrig is a preview and the foundation for future work — expect it to grow quickly.
IntelliJ 2025.3 (build 253) is no longer supported
The plugin no longer builds or runs against IntelliJ 2025.3 (253). The primary baseline
is now IntelliJ 2026.1 (261), with 2026.2 EAP (262) kept as a secondary
verification target: since-build = 261, and the managed-backend compatibility floor is also
261. That platform move brought the build to JDK 25, Kotlin 2.3.20, and Ktor
3.3.2, matching what the 2026.1 line bundles, and the build now fails earlier when a
JDK-25 or IDE-bundled-library assumption drifts. Android Studio support starts from the Quail 2.
steroid_execute_code gets an explicit modal mode
steroid_execute_code now takes a typed modal parameter instead of the earlier mix of
dialog-killer and allow-modal switches. There are three modes:
smart_non_modal— the default agent workflow: close stray dialogs, verify the IDE is
non-modal before sensitive work, commit documents, refresh VFS, and wait for smart mode.non_modal— asserts the IDE is non-modal at start only; no document sync, VFS refresh,
smart-mode wait, or mid-run dialog monitoring.unleashed— for intentional modal-dialog workflows.
The lower-level context methods (closeModalDialogs, monitorAndCloseModalDialogs,
syncDocuments, allowModalDialog) remain available inside scripts for cases that need finer
control. Modal-dialog behavior is now a clear contract rather than a set of ad-hoc booleans.
A narrower, more focused tool surface (10 → 8)
Staying true to the project's philosophy — give the agent the whole IDE through
steroid_execute_code and recipes, not a wide tool catalogue — two MCP tools were removed:
steroid_action_discoveryis gone; the same workflow now lives as the
mcp-steroid://ide/action-discoveryrecipe fetched throughsteroid_fetch_resource.steroid_apply_patchis gone; multi-site edits use the in-scriptapplyPatch { }DSL
fromsteroid_execute_code, guided by themcp-steroid://ide/apply-patchrecipe.
The MCP surface is now 8 focused tools. Two related changes for anyone upgrading from 0.95:
steroid_inputnow targets a window bywindow_id(fromsteroid_list_windows/
steroid_take_screenshot) instead of the oldscreenshot_execution_id— a breaking change
to that tool's input.- The
mcp-steroid://recipe corpus is now reached only throughsteroid_fetch_resource;
it is no longer advertised via the generic MCPresources/list/prompts/listsurfaces
(fetching the right IDE-conditional article needs the project context the tool carries).
Human review mode removed
The human-in-the-loop review gate has been removed in full — the review.* registry keys, the
mcp.steroid.review.mode system property, the execution-storage review-file helpers, the
review configuration classes, and the associated docs and website pages are all gone. The
product is focused on agent-driven IDE execution rather than a human-gated review step.
Other improvements
- Build-abort guidance. When a build is aborted without errors,
steroid_execute_codenow
appends a short "required action" hint pointing the agent at the Maven/Gradle sync recipe,
instead of leaving it to guess why the build produced nothing. - Token-efficient tabular output.
printCsvandprintToonhelpers were added to the
script context for compact tables insteroid_execute_codeoutput
(#34,
#35).
Infra & build
intellij-downloaderis now an in-repo Gradle subproject used by both the plugin build
and devrig's managed-backend path. It resolves and unpacks IntelliJ archives directly
(replacing the olduseInstallerpath), handles Community and Android Studio resolution, and
extracts Windows installers via a bundled 7-Zip — no external tooling required.- IDE downloads and managed-backend cache entries are hash-qualified so Community and
Ultimate archives that share a filename cannot collide. kotlinx-coroutines-coreis pinned to1.10.2andkotlinx-serializationto1.9.0to
match the 261 runtime. Two new gates —verifyBundledLibrariesand
verifyBundledKotlinxRuntime— fail the build on manifest-level or runtime-linkage drift.
These IDE-bundled jars are still never shipped inside the plugin zip.- The devrig↔plugin tool-call wire contract is documented as additive-only and pinned by
contract tests, including the fullsteroid_execute_codeparameter set
(#23). - All host-side test JVMs now run headless, and a large Docker suite exercises devrig end
to end — managed-backend provisioning and the stdio-agent matrix across Claude/Codex/Gemini. - The devrig CLI zip is now built and attached as a release artifact alongside the plugin zip.
Plugin Verifier
Verified against the primary target IntelliJ 2026.1 (261.22158.277): Compatible, 0
internal-API usages (the hard release gate) and 6 experimental-API usages. Against the
secondary EAP target 2026.2 (262.6653.22): Compatible, with 6 experimental-API usages
and 2 internal-API usages — two PluginManagerCore methods (getPlugin, getLoadedPlugins)
that 2026.2 newly marks internal. There is currently no public replacement available in both
2026.1 and 2026.2 (the successor PluginDetailsService exists only in 2026.2), so this is
tracked upstream with JetBrains as IJPL-246183
and will be migrated before 2026.2 ships.
Fixed issues
- #76 —
steroid_execute_codescripts
could fail with aClassCastExceptiononservice<T>()for split (content-module) plugins;
ideClasspath()/ the script classloader now include content-module classloaders. - #75 — implemented
resources/templates/listso MCP clients (e.g. Claude) no longer get a repeated
"Method not found". - #64 —
devrig install <agent>
auto-registers the MCP server with Claude / Codex / Gemini using the correct per-agent syntax. - #60 — the
steroid_execute_codetool
description now states the last expression is not auto-printed and to useprintln()/printJson(). - #52 —
steroid_execute_codenow runs in
thesmart_non_modalmode, which waits for smart mode before executing, so agent runs no longer
start while the project is still indexing. - #46 — an
steroid_execute_coderequest
cancelled or timed out under indexing now returns a clean cancellation result instead of an
opaque HTTP 500 (guarded by integration tests). - #53 — improved the debugger prompt recipes.
- #34,
#35 — added theprintToon/printCsv
token-efficient tabular output helpers, includingdictColumnspath de-duplication. - #23 — froze the devrig↔plugin tool-call
wire contract as additive-only and pinned it with contract tests. - #47,
#48,
#49,
#50,
#51 — hardened thesteroid_execute_code
prompts/recipes (path & anchor guessing, threading/action context, invented-helper APIs,
daemon-highlighting APIs, andapply_patchrecovery hints). - #77 — set up Plugin Verifier against
IntelliJ 2026.2 (262). - #63 — refreshed the
mcp-steroid://ide/inspect-and-fixrecipe for the 261 platform. - #61 — recipes/skill docs now flag
null-returning Platform lookups. - #59 — generation of the
.idea/mcp-steroid.mdport file is gated by themcp.steroid.idea.description.enabled
registry key (set itfalseto keep it out of the working tree). - #15 — documented how MCP Steroid differs
from IntelliJ's built-in MCP server (skill text + website). - #74,
#71 — closed as obsolete: the
steroid_action_discoverytool was removed (now themcp-steroid://ide/action-discoveryrecipe). - #72,
#57 — closed as won't-fix: the
steroid_apply_patchtool was removed in 0.100 and the remainingapplyPatch { }DSL is slated
for removal next release; edits go throughsteroid_execute_codeinstead.
Known issues
- #78 — on a Windows-side IDE opening a
WSL-hosted project,steroid_execute_codefails because the kotlinc spawn is routed into the
WSL distro (which has nocmd.exe). Workaround: set the registry key
mcp.steroid.storage.pathto a native Windows path (Find Action → "Registry…"), which moves the
per-execution working directory off the\\wsl$volume so the spawn targets Windows. A proper
fix is in progress.
Acknowledgements
Thanks to @andrii0lomakin for reporting the token-efficient
tabular-output helpers (#34,
#35), and for mentioning us at the
https://medium.com/@youtrackdb/beyond-the-dumb-zone-a-5-phase-autonomous-workflow-for-long-horizon-ai-agents-f14b034f2266.