

Aashish Ranjan Singh
237 posts

@_aashish_singh_
founder @ SteroidKit, the infrastructure layer for all coding platforms - https://t.co/FV7mdq76mG Hackathon Winner @ Meesho Dice, Adobe Papyrus Nebulae





There's a lot of buzz right now that MCP is dead and CLI is all we need. The reality is more nuanced. Consider two tasks: Task 1 — Git operations. CLI wins. - GitHub MCP server: 80 tools, ~55K tokens of schemas loaded upfront. Most agents use 1 or 2. - CLI does the same Git work in 2 bash commands the model already knows from training. Zero schema overhead. Task 2 — Read a Next.js webpage like modelcontextprotocal.io. MCP wins by 10×. - CLI agent tries curl, gets a JS bundle, ends up writing a Python script to reverse-engineer Next.js internals. Minutes. 2,000+ tokens. - MCP fetch tool: one call. 250 tokens. 2 seconds. Verdict: Use both. CLI for local jobs. MCP for external data interaction If your agent starts reverse-engineering a JS framework just to read a webpage — it picked the wrong tool. Found this gem today. A must watch from @IBM youtu.be/g9JIUM0MHgQ?si… via @YouTube









Managing API keys is one of the top security concerns we hear from customers. Today we’re introducing keyless auth for Claude Platform: authenticate via browser with the CLI, or let workloads use their existing cloud identity (AWS, GCP, Azure, or any OIDC token provider).





