v0.92.0

Release Date: April 8, 2026

Note: this plugin is currently tested only on macOS.

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.

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 mcp-steroid-0.92.0-59b78976.zip — Plugin ZIP
• Release page on GitHub

SHA-256: 8f01755fe14568315e59f70c6195e72878b3fbee928f1dacea6b8b52db5867e7

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

Highlights

MCP Steroid Is Now Open Source and Supported by JetBrains

MCP Steroid is now licensed under Apache 2.0 and officially supported by JetBrains. The full source is available for community contributions, audits, and forks. Read the full announcement: MCP Steroid Goes Open Source

Your IDE Skill Factory

MCP Steroid is more than a code-execution bridge — it is your IDE Skill Factory. Each prompt resource, each steroid_execute_code call, each debugging session is a scenario we collect and refine to make AI agents more capable in the IDE. Learn more and contribute yours: MCP Steroid as Skill Factory

Critical Bug Fix: Script Classpath (#16)

Content module JARs were missing from the script compile classpath. This caused compilation failures for code using classes from IDE content modules — including Kotlin plugin internals and Java API wrappers provided by bundled plugins. AI agents would receive unresolved reference errors even for APIs that are clearly available in the IDE.

The fix ensures that all JARs from loaded plugin classloaders are included when building the script classpath. (#16)

Exact Error Locations in Your Code

When something goes wrong, agents now see exactly where — in your code, not in the internal wrapper.

• Compiler errors now report the line number in the user-supplied code block, not in the generated wrapper class. A syntax error on line 3 of your snippet is now reported as line 3, not line 47.
• Runtime stack traces are remapped the same way: exception frames pointing into MCP Steroid’s wrapper code are translated to the original user-code line.
• Framework and wrapper frames are stripped from stack traces entirely, leaving only the frames that matter for diagnosis.

Cleaner Tool Output

Per-call boilerplate messages — FILE DISCOVERY, PRO Tip, TIP — have been removed from every tool response. These static hints were repeating on every invocation and adding noise without value. Output is now focused on execution results.

McpScriptContext Available as Prompt Resource

McpScriptContext — the object giving scripts access to the project, disposable, println(), progress(), and other IDE integration helpers — is now documented as a built-in MCP resource article. Agents can browse it via mcp-steroid://skill/coding-with-intellij.

Update Notification Now Includes Download Link

When a newer version of the plugin is available, the in-IDE update notification now shows a direct download link, making it faster to grab the latest release without navigating to the website.

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.