[{"data":1,"prerenderedAt":82},["ShallowReactive",2],{"r7OCp7VOVM":3,"i6xgKFEaah":5,"plugin-412":7,"versions-412":49},{"data":4},[],{"data":6},[],{"id":8,"name":9,"xmlId":10,"description":11,"preview":12,"docText":13,"email":13,"copyright":13,"downloads":14,"pricingModel":13,"purchaseInfo":13,"vendor":15,"tags":21,"themes":38,"icon":39,"iconDark":13,"iconHash":40,"programmingLanguage":13,"language":13,"licenseInfo":41,"isHidden":44,"screenshots":45,"updatedAt":46,"seo_title":9,"seo_description":12,"version":47,"iconUrl":48},412,"MCP Steroid","com.jonnyzzz.mcp-steroid","\u003Cp>\u003Cstrong>MCP Steroid\u003C/strong> brings the full power of the IntelliJ Platform to AI agents through the Model Context Protocol (MCP).\u003C/p>\n\n    \u003Cp>\u003Cb>IntelliJ platform works for AI agents as great as for human developers.\u003C/b>\u003C/p>\n\n    \u003Cp>MCP Steroid is an independent research project by Eugene Petrenko (\u003Ca href=\"https://jonnyzz.com\">@jonnyzzz\u003C/a>). Not affiliated with, endorsed by, or supported by JetBrains s.r.o.\u003C/p>\n\n    \u003Ch3>What You Get\u003C/h3>\n    \u003Cul>\n        \u003Cli>\u003Cb>9 MCP Tools:\u003C/b> Control IntelliJ IDEA programmatically - execute code, take screenshots, discover actions, debug, and more\u003C/li>\n        \u003Cli>\u003Cb>80+ MCP Resources:\u003C/b> Comprehensive guides covering LSP, IDE operations, debugger, tests, VCS, and more\u003C/li>\n        \u003Cli>\u003Cb>Vision Capabilities:\u003C/b> AI agents can see your IDE with screenshots and OCR (unique to MCP Steroid)\u003C/li>\n        \u003Cli>\u003Cb>Deep Integration:\u003C/b> Access PSI, inspections, refactorings, and full IntelliJ Platform API\u003C/li>\n        \u003Cli>\u003Cb>Human Oversight:\u003C/b> Review and approve code execution with configurable safety controls\u003C/li>\n    \u003C/ul>\n\n    \u003Ch3>Why MCP Steroid?\u003C/h3>\n    \u003Cp>Unlike LSP-only solutions, MCP Steroid gives AI agents the same powerful IDE capabilities that developers use - semantic understanding, advanced refactorings, debugging, test running, and visual awareness.\u003C/p>\n\n    \u003Cp>\u003Cb>Compatible with all IntelliJ Platform-based IDEs:\u003C/b> IntelliJ IDEA, PyCharm, WebStorm, GoLand, CLion, Rider, and more.\u003C/p>\n\n    \u003Cp>\u003Cb>Requirements:\u003C/b> IntelliJ IDEA 2025.3 or newer (build 253 or later)\u003C/p>\n\n    \u003Cbr>\n    \u003Ch3>Demo: CodeDozer & IntelliJ Debugger\u003C/h3>\n    \n    \u003Cbr>\u003Cbr>\n\n    \u003Cp>Visit \u003Ca href=\"https://mcp-steroid.jonnyzzz.com\">https://mcp-steroid.jonnyzzz.com\u003C/a> for documentation and examples.\u003C/p>\n\n    \u003Cp>\u003Csmall>IntelliJ IDEA, IntelliJ Platform, PyCharm, WebStorm, and JetBrains are trademarks of JetBrains s.r.o.\u003C/small>\u003C/p>","MCP Steroid brings the full power of the IntelliJ Platform to AI agents through the Model Context Protocol (MCP). IntelliJ platform works for AI agents as great as for...",null,0,{"name":16,"url":17,"link":18,"publicName":19,"email":20},"fd5e8b72-4d41-4569-a96e-d9d7cc747237","https://jonnyzzz.com","","jonnyzzz.com","me@jonnyzzz.com",[22,26,30,34],{"id":23,"name":24,"link":18,"families":25},4,"Code Tools",[],{"id":27,"name":28,"link":18,"families":29},8,"Code Editing",[],{"id":31,"name":32,"link":18,"families":33},22,"Debugging",[],{"id":35,"name":36,"link":18,"families":37},60,"AI",[],[],"plugins/com.jonnyzzz.mcp-steroid/default.svg","d8e9fa82dbdd9246e2a3c752c3b4a24f69c08e09d6c506067cc65c881c6ca0fd",{"licenseType":42,"licenseUrl":43},"Custom/Unknown","https://mcp-steroid.jonnyzzz.com/LICENSE",false,[],"18.04.2026","0.93.0-effb0b5a","/images/412/icon.svg",{"0":50},{"year":51,"id":52,"cards":53},2026,"id_0",[54,71],{"id":55,"version":47,"cdate":56,"downloadUrl":57,"notes":58,"since":59,"until":18,"sinceUntil":60,"channel":13,"size":61,"downloads":14,"pluginId":8,"compatibleVersions":62,"author":63,"modules":68,"dependencies":69,"hidden":44,"year":51},2299,"1776496352000","plugins/com.jonnyzzz.mcp-steroid/0.93.0-effb0b5a/mcp-steroid-0.93.0-effb0b5a.zip","\u003Cpre>## 0.93.0\n\n### Plugin Verifier Compliance: Fewer Internal API Usages\n\nSix internal IntelliJ API usages have been replaced with public or experimental alternatives. The plugin verifier now reports only 4 unavoidable internal API references (where no public alternative exists) — down from 29.\n\nKey replacements:\n- `PluginMainDescriptor` → public `IdeaPluginDescriptor.contentModules` extension\n- `DaemonCodeAnalyzerImpl.getLineMarkers()` → public `DocumentMarkupModel` API\n- `AppLifecycleListener.appStarted()` → public `appFrameCreated()`\n- `OpenProjectTask` internal builder → public `build().copy()`\n- `serviceAsync<T>()` → stable `service<T>()`\n- `writeAction {}` → stable `edtWriteAction {}` in ReviewManager\n\n### MCP Server Instructions Rewritten\n\nThe instructions agents see when they connect to MCP Steroid are now concise and exec_code-first:\n- Declares MCP Steroid as a **stateful API** and **drop-in replacement for LSP**\n- Three-step getting started: `list_projects` → `fetch_resource` → `execute_code`\n- Removed the skill guide routing table that agents never read (0/69 arena runs)\n\n### New Tool: `steroid_fetch_resource`\n\nA new MCP tool for loading `mcp-steroid://` skill guides. Task-aware description maps intent to the right resource:\n- Running tests? → `mcp-steroid://prompt/test-skill`\n- Debugging? → `mcp-steroid://prompt/debugger-skill`\n- Any IDE task? → `mcp-steroid://prompt/skill`\n\n### Improved `steroid_action_discovery`\n\nThe tool description now explains the discovery→exec_code workflow: call action_discovery first to learn available quick-fixes and gutter actions, then invoke them via `steroid_execute_code`.\n\n### Maven Test Execution Fix\n\nFixed a critical bug where the ModalityStateMonitor killed Maven test execution prematurely. `MavenShCommandLineState.startProcess()` uses `runWithModalProgressBlocking`, which creates a `JobProviderWithOwnerContext` — a coroutine-based progress entity, not a UI dialog. The monitor now skips `JobProvider` entities.\n\n### Integration Tests for Maven and Gradle Test Execution\n\nNew Docker-based integration tests validate end-to-end test execution:\n- **MavenTestExecutionTest**: Maven tests via `ProgramRunnerUtil.executeConfiguration()` with process exit code validation\n- **GradleTestExecutionTest**: Gradle tests via `GradleRunConfiguration.setRunAsTest(true)` + SMTRunner events\n\n### Hardcoded URI Lint Rule\n\nNew `NoHardcodedMcpSteroidUriUsageTest` enforces that production code uses generated `XxxPromptArticle().uri` instead of hardcoded `mcp-steroid://` string literals. Comprehensive KDoc documents how to fix violations.\n\n### CI and Infrastructure\n\n- GitHub Actions: `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24` added to all workflows\n- TeamCity: artifact post-processing for 1080p video + slim zip\n- `escapeShellArgs` properly quotes glob/meta characters for Docker exec\n- Linux bind-mount UID handling for TC agents\n- Codex default model updated to `gpt-5.4`, Gemini to `gemini-3.1-pro-preview`\n\n### Cleanup\n\n- Removed all `steroid_capabilities` references (tool was removed)\n- Fixed `steroid_open_project` docs (trust_project defaults to true, removed non-existent force_new_frame parameter)\n- Updated resource access guidance to use `steroid_fetch_resource` instead of `ReadMcpResourceTool`\n- Plugin description now says \"80+ MCP Resources\" (was stale \"58\")\u003C/pre>\u003C/ul>","253.0","253.0+",194003926,{},{"id":64,"name":65,"link":66,"hubLogin":67},"348","Eugene Petrenko","/author/fd5e8b72-4d41-4569-a96e-d9d7cc747237","jonnyzzz",[],[70],"com.intellij.modules.platform",{"id":72,"version":73,"cdate":74,"downloadUrl":75,"notes":76,"since":59,"until":18,"sinceUntil":60,"channel":13,"size":77,"downloads":14,"pluginId":8,"compatibleVersions":78,"author":79,"modules":80,"dependencies":81,"hidden":44,"year":51},2297,"0.92.0-59b78976","1775648137000","plugins/com.jonnyzzz.mcp-steroid/0.92.0-59b78976/mcp-steroid-0.92.0-59b78976.zip","\u003Cpre>## 0.92.0\n\n### MCP Steroid Is Now Open Source and Supported by JetBrains\n\nMCP Steroid is now licensed under **Apache 2.0** and officially supported by JetBrains. This release marks a milestone for the project — the full source is available for community contributions, audits, and forks. Read the full announcement: [MCP Steroid Goes Open Source](https://jonnyzzz.com/blog/2026/04/07/mcp-steroid-open-source/)\n\n### Your IDE Skill Factory\n\nMCP 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. We are actively gathering real-world workflows. Learn more and contribute yours: [MCP Steroid as Skill Factory](https://jonnyzzz.com/blog/2026/04/08/mcp-steroid-skill-factory/)\n\n### Critical Bug Fix: Script Classpath (#16)\n\n**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.\n\nThe fix ensures that all JARs from loaded plugin classloaders are included when building the script classpath. ([#16](https://github.com/jonnyzzz/mcp-steroid/issues/16))\n\n### Exact Error Locations in Your Code\n\nWhen something goes wrong, agents now see exactly where — in **your code**, not in the internal wrapper.\n\n- **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.\n- **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.\n- **Framework and wrapper frames** are stripped from stack traces entirely, leaving only the frames that matter for diagnosis.\n\n### Cleaner Tool Output\n\nPer-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.\n\n### McpScriptContext Available as Prompt Resource\n\n`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`.\n\n### Update Notification Now Includes Download Link\n\nWhen 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.\u003C/pre>\u003C/ul>",186553375,{},{"id":64,"name":65,"link":66,"hubLogin":67},[],[70],1776947850674]