Been following what’s happening in the CLI + AI agent space and the signals are everywhere: Google just launched Google Workspace CLI with built-in MCP server and 100+ agent skills. Got 4,900 stars in 3 days. Guillermo Rauch (Vercel CEO): “2026 is the year of Skills & CLIs” Karpathy called out the new stack: Agents, Tools, Plugins, Skills, MCP. Said businesses should “expose functionality via CLI or MCP” to unlock agent adoption. This got me thinking. Most of us are building APIs every day, we have OpenAPI specs lying around, but no easy way to make them agent-friendly. So I spent some time and built agent-ready-cli . You give it any OpenAPI spec and it generates: A full CLI with –dry-run , –fields , –help-json , schema introspection An MCP server (JSON-RPC over stdio) that works with Claude Desktop / Cursor Prompt-injection sanitization and input hardening out of the box One command, that’s it: npx agent-ready-cli generate --spec openapi.yaml --name my-api --out my-api.js --mcp my-api-mcp.js I validated it against 11 real SaaS APIs (Gitea, Mattermost, Kill Bill, Chatwoot, Coolify, etc.) covering 2,012 operations total. It handles both OpenAPI 3.x and Swagger 2.0. Would love feedback from the community. If you have an OpenAPI spec, try it out and let me know what breaks. GitHub: https://github.com/prajapatimehul/agent-ready submitted by /u/eager_mehul
Originally posted by u/eager_mehul on r/ClaudeCode