by ops0-ai · MCP Server · ★ 74
ops0 CLI Policy, lint, vulnerability, and cost guardrails for AI coding agents. Sits in front of Claude Code, Codex and Gemini CLI. Every time the agent finishes writing IaC, the whole working directory gets validated, linted, policy-checked, security-scanned, and cost-estimated server-side. Failures come back as a failed tool call so the agent self-remediates. Destructive commands are blocked before they run. Quick start · What runs at end-of-turn · How agents trigger it · Monorepos · ops0-scan.md · Commands Why this exists When humans write infrastructure, policy gates fire on the PR.
| Stars | 74 |
| Forks | 3 |
| Language | Go |
| Category | MCP Server |
| Quality Score | 65.9491249562043/100 |
| Open Issues | 4 |
| Last Updated | 2026-07-06 |
| Created | 2025-06-10 |
| Platforms | claude-code, cli, codex, gemini, go, mcp |
| Est. Tokens | ~19k |
These tools work well together with ops0-cli for enhanced workflows:
Explore other popular mcp server tools:
ops0-cli is Stop your AI agent from shipping insecure IaC. ops0 CLI sits between Claude Code, Codex or Gemini and your cloud, scanning every .tf the agent writes and blocking destroy commands before they run.. It is categorized as a MCP Server with 74 GitHub stars.
ops0-cli is primarily written in Go. It covers topics such as ai-agents, audit-log, claude-code.
You can find installation instructions and usage details in the ops0-cli GitHub repository at github.com/ops0-ai/ops0-cli. The project has 74 stars and 3 forks, indicating an active community.