| Tbh I find self-documenting CLIs (e.g. with a `--help` flag, and printing correct usage examples when LLMs make things up) plus a skill that's auto invoked to be pretty reliable. CLIs can do OAuth dances too just fine. MCP's remaining moats I think are: - No-install product integrations (just paste in mcp config into app) - Non-developer end users / no shell needed (no terminal) - Multi-tenant auth (many users, dynamic OAuth) - Security sandboxing (restrict what agents can do), credential sandboxing (agents never see secrets) - Compliance/audit (structured logs, schema enforcement)? If you're a developer building for developers though, CLI seems to be a clear winner right |
But since when has this industry done the right thing informed by wisdom and hindsight?