MORE CONTEXT. FEWER TOKENS. ZERO BLOAT.Free — no credit card required
BRING YOUR CODING AGENT ON
STEROIDS.
The ultimate ecosystem for your coding agent — cross-IDE recall that remembers every past conversation, 200+ MCP servers through 2 tools, zero-cost cloud AI workflows powered by your IDE’s LLMs, and a local vault that keeps secrets off LLM context. One CLI syncs it all.
>
CONTEXT-MAXXING.
Steroid recall carries your history across every supported IDE, surfacing only what's relevant — so no new chat starts from zero, without blowing your token budget.
Recall works identically in Claude Code, Cursor, Codex, and Copilot — memory isn't locked to one editor.
Every session is auto-synced the moment it ends. No manual save, no export.
Recall runs and stores entirely on your machine. Nothing leaves it — even in Connected mode.
QUICK_INSTALLATION
ONE COMMAND.
YOU'RE RUNNING.
Install the CLI, then run steroid.
MACOS / LINUX
INSTALL
$
curl -fsSL https://raw.githubusercontent.com/steroidkit/releases/main/install.sh | sh
LAUNCH
$
steroid
WINDOWS (POWERSHELL)
INSTALL
>
irm https://raw.githubusercontent.com/steroidkit/releases/main/install.ps1 | iex
LAUNCH
>
steroid
No account needed for Local mode.
CLI MODES.
Start local and private. Connect when you want the marketplace and workflows.
Conversation-memory recall
Cross-IDE context (Claude Code, Cursor, Codex, Copilot)
Auto-synced chat history
No server — fully local
No sign-up. Nothing leaves your machine.
Everything in Local, plus:
Recall + cross-IDE context, one command install, wires every IDE automatically.
200+ tool servers through 2 calls. Zero context bloat.
Deterministic workflow automation exposed as REST APIs.
AES-encrypted secrets, shared across every IDE. The LLM never sees them.
Connected is a strict superset — it never removes what Local gives you.
STEROID CLI
What it is
One command-line tool that installs on macOS, Windows, and Linux, indexes every conversation across every connected IDE for instant recall, and wires each editor to a shared MCP gateway and Vault. Open a fresh session in Cursor after finishing a task in Claude Code — the CLI already knows what happened. Add a credential once, every IDE sees it. No per-IDE setup. No JSON files.
Features
Cross-IDE conversation recall, auto-detected IDE configuration, always-fresh background memory sync, shared Vault and tool catalog across every editor, TUI onboarding, and self-update.
ALL
IDEs, One Memory
3
Operating Systems
ZERO
Per-IDE Configuration
STEROID MCP
What it is
A unified MCP gateway that exposes 200+ servers through exactly 2 tools — search_tools and run_tool. Your agent searches for what it needs at runtime and executes it, instead of loading every server upfront. No context bloat, no hallucinated tool names. The gateway runs tools on your behalf and does not store inputs, outputs, or credentials — your data does not remain with us.
Features
Dynamic discovery, isolated execution, secure credential injection, and cryptographic capability tokens for deterministic tool eligibility, and no retention of tool inputs, outputs, or credentials.
95+%
Context Reduction
50+%
Cost Savings
100%
Isolated Execution
STEROID FLOWS
What it is
A deterministic flow builder for AI workflows. Instead of prompting an agent to follow steps and hoping it does, you define each step as a block — LLM nodes, MCP blocks, conditionals, webhooks — and the engine executes them in order, every time, with full tracing.
Features
Workflows exposed as REST APIs, SSE webhooks for real-time updates, LLM nodes powered by your IDE/Coding Agent subscription, efficient data flow between nodes.
98.6%
Reduction in Bugs
97%
Cost Savings
100%
Reliability Rate
STEROID VAULT
What it is
An encrypted credential store shared across every IDE connected to the Steroid ecosystem. API keys never appear in config files, never touch LLM context, and never get logged. You don't even need to enter secrets upfront — when your agent runs a tool for the first time and the credential is missing, Steroid MCP elicits it during execution, stores it securely in the Vault, and from the next run onward the secret is injected automatically. The LLM simply asks for the tool — it has zero awareness of the secret management happening underneath.
Features
Just-in-time secret elicitation on first use, automatic injection on subsequent runs, cross-IDE credential sharing, zero-trust session-bound tokens, and AES-encrypted local storage with tamper detection.
0%
Plaintext Exposure
BLOCK
Structural Leakage
AES
Encryption Grade
THE NUMBERS DON'T LIE.
Every number below is sourced. Every problem is live in production today. Every fix ships with Steroid Kit.
| PROBLEM | THE REALITY | WITH STEROID KIT |
|---|---|---|
Context Window Bloat | Connect GitHub, Slack, and Sentry — 3 servers, ~40 tools — and 55K tokens are gone before your agent reads a single message. GPT-5 scores just 43.7% on real-world MCP tasks. Tool accuracy degrades rapidly as servers scale. | STEROID MCP 200+ servers through 2 tools. ~500 tokens total overhead. 99.7% of your context preserved. |
Tool Hallucination | Even frontier models complete only 43–54% of real-world MCP tool tasks. Smaller reasoning models hallucinate tools up to 74% of the time — and alignment cuts it to 56% while degrading utility. Tool accuracy collapses as servers scale. | STEROID MCP FSM-enforced workflows + cryptographic capability tokens. The LLM can only call tools it discovered — hallucinated execution is structurally impossible. |
Plaintext Secrets | 100% of MCP setups store API keys in plaintext JSON. Indirect prompt injection exfiltrates credentials with up to 88% success. 315 MCP vulnerabilities identified in 2025 alone. | STEROID VAULT AES-encrypted local vault. Secrets elicited just-in-time on first use, then injected automatically. Shared across every connected IDE. The LLM never sees credentials — it just calls the tool. |
Skills Can't Orchestrate | Skills embed workflow instructions in plain text — the LLM can skip, reorder, or hallucinate steps. SkillsBench shows top models achieve only 44–49% success even with curated skill scripts across 84 tasks. Without enforcement, a skill saying "commit, update Jira, write Confluence wiki" is a suggestion — not a guarantee. | STEROID FLOWS Replace instructions with a Flow API call. The skill triggers one endpoint — the flow engine enforces every step end-to-end. The LLM can't skip what it doesn't control. |
Skills Run on Hope | Today's skills rely on plain-text instructions and shell scripts executed in sequence — the LLM decides whether to follow them. A 10-step skill at 95% per-step reliability delivers only 59.9% end-to-end success. Scripts break across OS, shells, and environments. There is no retry, no tracing, and no guarantee any step ran. | STEROID FLOWS Replace scripts with a Steroid Flows API call. The skill triggers one endpoint — the flow engine handles every step with full tracing, retries, and 100% execution guarantee. Same skill, 4× more reliable, works identically on every OS. |
No Tool → API Bridge | You can build a skill, but you can't expose a multi-tool AI workflow as a REST endpoint. There's no bridge between "LLM can use tools" and "my system can call a reliable pipeline." | STEROID FLOWS Set a webhook trigger, chain tool nodes + LLM nodes, end with a response node — your workflow is now a REST API. 1 flow, callable from anywhere. |
Token Cost Explosion | MCP costs 4–32× more tokens than alternatives. One user's 3-server setup turned a $2 chat into $47. Monthly at 10K ops: $3.20 (CLI) vs $55.20 (MCP). | STEROID MCP Constant low overhead regardless of server count. Search + run architecture — nothing loaded upfront. |
Setup Hell | 7–12 manual steps per server. JSON editing, env vars, restarts, debugging — per IDE, per server. 70% of devs manage 2–7 servers simultaneously. | STEROID CLI 1 curl command. IDE configured, vault set up, 200+ servers ready. Zero re-configuration. |
Zero Sandboxing | Local MCP servers run with full user permissions. Files, network, env vars — all exposed. 50% of builders cite security as their #1 challenge. | STEROID MCP Cloud-isolated runtimes. No foreign code runs on your machine. Request in, response out. |
Ecosystem Chaos | 16,000+ MCP servers. 97M+ monthly SDK downloads. No unified access. Every developer reinvents the wheel. | STEROID MCP One gateway. 200+ curated servers. Access grows automatically — every server doubles as a block in your flows. |
WHERE STEROID RUNS.
C
Cursor
Full support via Steroid CLI
CC
Claude Code (CLI)
Full support via Steroid CLI
GH
GitHub Copilot
Full support via Steroid CLI
CX
Codex
Full support via Steroid CLI
AG
Antigravity
Coming soon
// Don't see your IDE? Use the button above to request support.
READY_FOR_UPGRADE
REWIRE YOUR
AGENTIC_IDE.
Free for individual developers. Always. Steroid Kit is a platform — the ecosystem grows as developers contribute flows and skills.