# mcp-steroid Published articles for mcp-steroid. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Install, Launch, Update: Shipping a CLI on Five Platforms -- the devrig Approach DevFeed: [Install, Launch, Update: Shipping a CLI on Five Platforms -- the devrig Approach]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-08-06T00:00:00Z Content type: tutorial Language: en Sources: [Eugene Petrenko]() Topics: [Command-line interface](), [Kotlin](), [ide]() Tags: [agents](), [ai-agents](), [ai-coding](), [architecture](), [cli](), [command-line](), [devrig](), [distribution](), [eugene-petrenko](), [jdk](), [jonnyzzz](), [jvm](), [kotlin](), [mcp-steroid](), [open-source](), [sha-256](), [tag-41199d53f463]() ### AI overview This tutorial presents the devrig approach to distributing and updating a JVM command-line tool across five platforms. It describes generated install scripts with verified JDK coordinates and baked-in URLs and SHA-256 hashes, content-addressed side-by-side installations, binary-owned launchers, and updates performed by running a fresh install script. ### Source excerpt A JVM command-line tool is easy to write and miserable to ship. You need five platforms, a JDK the user does not have, an update path that never overwrites a running install, and a trust story for a `curl | sh` one-liner. Here is the architecture we ended up with in `devrig`: generate the install script from a model whose JDK coordinates are signature-verified, make installs content-addressed and side-by-side, let the binary own its own launcher, and make "update" mean nothing more than running a fresh install script ## A Real IntelliJ IDEA Inside Docker: Integration Tests with X Server, Window Manager, and Live Video DevFeed: [A Real IntelliJ IDEA Inside Docker: Integration Tests with X Server, Window Manager, and Live Video]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-07-05T00:00:00Z Content type: tutorial Language: en Sources: [Eugene Petrenko]() Topics: [IntelliJ IDEA](), [Docker](), [Testing](), [Docker Container](), [FFmpeg (Fast Forward Moving Picture Experts Group)](), [GUI](), [Node.js](), [MCP]() Tags: [ai-agents](), [ai-coding](), [browser](), [devrig](), [docker](), [docker-container](), [eugene-petrenko](), [ffmpeg](), [gui](), [intellij](), [intellij-idea](), [jonnyzzz](), [mcp](), [mcp-steroid](), [node-js](), [plugin](), [tag-41199d53f463](), [testing](), [tests]() ### AI overview This tutorial presents a reusable approach for running full IntelliJ IDEA integration tests inside Docker with a GUI. It covers the container image, X server, window management, IDE control, and streaming live video to a browser, with open-source code in the test-integration module. ### Source excerpt Evals that boot a full IntelliJ IDEA -- pixels, dialogs, indexing and all -- inside a Docker container. Xvfb provides the display, fluxbox keeps the windows in place, ffmpeg records everything, and a tiny Node.js server streams the live video straight into a browser tab on your machine. Here is the whole recipe, so you can build your own. ## devrig: MCP Steroid Goes Level 3 -- Autonomous IDE Setup for AI Agents DevFeed: [devrig: MCP Steroid Goes Level 3 -- Autonomous IDE Setup for AI Agents]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-06-02T00:00:00Z Content type: article Language: en Sources: [Eugene Petrenko]() Topics: [Model Context Protocol (MCP)](), [AI Agent](), [IntelliJ IDEA](), [Command-line interface](), [Claude](), [Keycloak]() Tags: [agent](), [agentic-experience](), [ai-agent](), [ai-agents](), [ai-coding](), [claude](), [cli](), [devrig](), [eugene-petrenko](), [intellij](), [jonnyzzz](), [keycloak](), [mcp](), [mcp-steroid](), [tag-41199d53f463]() ### AI overview The article presents Level 3 of MCP Steroid, where the devrig CLI autonomously configures an agent's MCP connection and downloads or starts an IntelliJ-family IDE. Its end-to-end test reports that Claude found 4,633 PSI usages of a class in Keycloak in one prompt. ### Source excerpt The new `devrig` CLI in MCP Steroid 0.100 turns the IDE bring-up ritual into one stdio command. `devrig install ` writes the MCP config; `devrig backend download/start` brings an IntelliJ-family IDE into existence and gives the agent an IDE of its own. In the e2e test, Claude provisions an IDE and finds 4,633 PSI usages of one class in Keycloak -- in one prompt. ## From HTTP MCP to stdio: Lessons Connecting an AI Agent to a Desktop IDE DevFeed: [From HTTP MCP to stdio: Lessons Connecting an AI Agent to a Desktop IDE]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-05-20T00:00:00Z Content type: article Language: en Sources: [Eugene Petrenko]() Topics: [Model Context Protocol](), [IntelliJ IDEA](), [AI Agent](), [Command-line interface](), [Cross-origin resource sharing (CORS)]() Tags: [agentic-coding](), [ai-agent](), [ai-agents](), [ai-coding](), [architecture](), [claude](), [cli](), [codex](), [devrig](), [docker-image](), [eugene-petrenko](), [integration-test](), [intellij](), [jonnyzzz](), [kotlin](), [ktor](), [mcp](), [mcp-steroid](), [report](), [tag-41199d53f463]() ### AI overview This article explains why an HTTP MCP server embedded in a desktop IntelliJ application proved unreliable on real workstations. It describes moving to stdio with a CLI coordinator called devrig, and emphasizes integration tests for the MCP layer, including issues involving dynamic ports, startup ordering, multiple IDEs, and mismatched transport support. ### Source excerpt The obvious way to connect an AI Agent to a running IntelliJ is an HTTP MCP server inside the IDE. I built it, shipped it, and used it daily -- and it kept breaking on real workstations: dynamic ports, start-order lottery, multiple IDEs, and the agent-up/IDE-down dead end. Here is why I moved the whole thing to stdio and a CLI coordinator called devrig, and what the journey taught me. ## 130 Release-Roadmap Issues, 818 Agent Runs: A Mid-Iteration Reality Check DevFeed: [130 Release-Roadmap Issues, 818 Agent Runs: A Mid-Iteration Reality Check]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-04-28T00:00:00Z Content type: article Language: en Sources: [Eugene Petrenko]() Topics: [AI Agent](), [Claude](), [codex](), [Artificial Intelligence](), [issue tracker](), [Orchestration](), [Command-line interface](), [Graphs](), [Requirements]() Tags: [agent](), [agents](), [ai](), [ai-agent](), [ai-agents](), [ai-coding](), [cli](), [code](), [eugene-petrenko](), [graph](), [issue-tracker](), [jonnyzzz](), [mcp](), [mcp-steroid](), [multi-agent](), [orchestration](), [pipeline](), [requirements](), [run-agent](), [tag-41199d53f463]() ### AI overview The article describes using a swarm of Claude, Codex, and Gemini agent CLIs to research 130+ release-roadmap issues and produce implementation specifications. The process used 818 agent runs over four days at an approximately $576 cost, followed by a mid-release comparison of the research with the team's actual work. ### Source excerpt We turned one release's roadmap -- 130+ umbrella-epic issues -- into fully-researched implementation specs using a swarm of three different agent CLIs (Claude, Codex, Gemini): 818 runs, ~155M+ tokens, ~$576, four days. Then, mid-release-cycle, we ran a snapshot to compare the research against reality -- with no expectation that anything was "done" yet. Here is the pipeline, the numbers, and the honest verdict.