v0.94.0

This release is obsolete. Please use the latest release: v0.101

MCP Steroid v0.94.0 — IntelliJ for AI Agents, not humans. New atomic multi-file steroid_apply_patch tool, periodic DialogKiller, Maven/Gradle prompt resources, and zero internal-API usages.

Release Date: May 5, 2026

Highlights

New Tool: steroid_apply_patch

Atomic multi-file batch edits in a single MCP call. Input: {project_name, hunks: [{file_path, old_string, new_string}, ...]}. All hunks land inside one WriteCommandAction (“MCP Steroid: apply-patch (N hunks)”); per-file descending offset order; pre-flight rejects missing or non-unique old_string matches before touching any document; touched documents are saved before the call returns. Microshop-2 benchmark: 8 hunks across 8 files in ~66 ms, zero Edit fallbacks. Same engine is exposed in scripts as applyPatch { hunk(file, old, new); ... } on McpScriptContext.

New MCP Resources

Rewritten Resources

DialogKiller Replaces ModalityStateMonitor

The 236-line ModalityStateMonitor is gone. DialogKiller runs as a periodic EDT poll, dismisses real DialogWrapper windows, and ignores coroutine progress entities and elevated ModalityState.any() blocks. Side effects: Maven and Gradle test runs no longer get cancelled mid-flight; SDK-lookup banners stop being flagged as modals. New per-call dialog_killer: true|false parameter on steroid_execute_code lets a script opt in/out.

Bug Fixes

Output Hints from steroid_execute_code

VfsRefreshService

New project-level service. CodeEvalManager calls awaitRefresh() (suspending, 30 s cap) before kotlinc compiles a script, and scheduleAsyncRefresh() (fire-and-forget) in the finally after every steroid_execute_code and steroid_apply_patch call. PSI sees up-to-date files between back-to-back script calls without callers writing their own refresh boilerplate.

Plugin Verifier: Zero Internal-API Usages

Building on 0.93.0’s reduction (29 → 4): the action-group expansion path was the last avoidable internal-API call. The 0.94.0 binary reports 0 internal-API usages against both IntelliJ 2025.3 and 2026.1 under Plugin Verifier. Three experimental references remain — all of them public replacements that IntelliJ itself flags as experimental (IdeaPluginDescriptor.contentModules, suspending writeAction).

~10× Faster No-Change TDD Loop

External contributor Dmitry Protsenko (@NordCoderd) traced four orthogonal sources of cache invalidation in the build (#26): LocalDateTime.now() outside deployPlugin invocations (kept generateMetadata out-of-date), the orphaned Random.nextInt() seed in GenerateMetadataTask, missing inputs/outputs on npmBuild, and per-run If-Modified-Since round-trips for tessdata. Atomic OCR + Kotlin compiler downloads guard against corrupted-on-disk files. No-change ./gradlew :ij-plugin:test drops from ~28 s to ~3 s.

SDK-Lookup Modal Hardening

Three independent IntelliJ entry points fire an “Unknown SDK” / “Resolving SDKs…” modal on project open. The plugin now disables all three (-Dunknown.sdk=false, -Dunknown.sdk.auto=false, -Dunknown.sdk.modal.jps=false) and ships mcpListJdks / mcpAddJdk / mcpRegisterJdks driver helpers. Pre-registers bare/corretto-N/temurin-N aliases for every JDK on the agent before the IDE’s SdkLookup task can race in. JDK setup is skipped cleanly on non-Java IDEs (PyCharm, GoLand, WebStorm, Rider).

Other

Download

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

  1. Download the .zip file 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.

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 for the plugin. 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

Contributors

Thank you to the contributors in this release:

Proof-of-Concept & Support

MCP Steroid is built by Eugene Petrenko, with 21 years of JetBrains ecosystem experience.

We run Proof-of-Concept engagements for company-specific use cases — custom skills, internal tooling integrations, AI Agent workflows tailored to your codebase. Learn more about consulting and Proof-of-Concept options.

Beyond GitHub Sponsors, MCP Steroid also accepts in-kind support: compute tokens for evaluation runs, hardware for the multi-IDE test matrix, and licenses for benchmarking and observability tools. If you or your organisation would like to back the project or the research behind it on those terms, reach out — contact details are linked below.