Documentation
Learn how to install, configure, and use MCP Steroid with your AI Agents.
Getting Started
Getting Started
Install devrig, register your AI agent, and add the MCP Steroid plugin
Read more →What your AI agent can do
The IDE actions devrig and MCP Steroid give your coding agent, who it helps, and the agents and IDEs it works with
Read more →devrig CLI
A standalone CLI that registers MCP Steroid with your AI Agent, bridges it to a running IDE, and can download and start a managed IntelliJ backend
Read more →Support the Project
Share reproducible scenarios to help improve MCP Steroid on real repositories
Read more →Vision
How it works
How MCP Steroid exposes IntelliJ as an MCP server that AI Agents can call over HTTP
Read more →Experiment Findings: IDE vs Shell Agents
Measured A/B results — the same coding tasks with and without MCP Steroid, on real codebases, with evidence-based scoring
Read more →Strategy
How MCP Steroid helps your AI agent change code with fewer cleanup loops
Read more →Project Assessment — 2026-02-22
Comprehensive development assessment covering codebase architecture, commit velocity, test coverage, and executive vision for MCP Steroid
Read more →Reinforced Learning Approach
How MCP Steroid improves agent reliability with reproducible experiments
Read more →IntelliJ as a Skill Factory
Build reusable agent skills from IntelliJ APIs without plugin development
Read more →Archived: early DPAIA wall-clock table
The early DPAIA wall-clock comparison, kept for the record only — withdrawn as current evidence
Read more →Reference
Connect your AI Agents
How to find and copy your MCP server connection details from the IntelliJ Settings page
Read more →Running devrig in CI
Run devrig with an attended IDE under Xvfb/GUI, or with the supported frontendless IDEA Ultimate Remote Development backend
Read more →MCP Steroid Configuration
Registry keys and settings for MCP Steroid
Read more →