Eldodi

With the v2 spec, MCP became a lot closer to APIs by becoming stateless. And there is now a push to use HTTP verbs more extensively to improve caching even better in v3. MCP is converging into APIs but wit great auth and auditing

A shame agents will never read this, just like they almost never read llms.txt or try to get the .md version of your html pages!

Is it really contrarian though? Cohere, Aleph Alpha and many other model companies went that route and are doing well

MCP usage is at an all-time peak - 17M daily (!) downloads of the official SDKs.

We're using MCP for virtually all our SaaS and infra providers (CRM, ATS, banking and accounting, Notion, Linear, all dev tools and hosting platforms) it's become a hard requirement in our buy bechmark. No MCP = NOGO

The advantages are:

- baked-in auth: no need to configure anything, it just works with our employees accounts

- one click install with Codex Plugins and Claude Connectors

APIs and WebMCP don't have the same purpose:

- WebMCP allows agents to assist humans on their own interface ie the web UI.

- APIs bypass the human interface completely

And I'm not sure most of the work today is done on legacy desktop apps. We're in 2026, not 2016

it's not a question of model size, it's a question of your model API engineering. The initial problem was that the all tools schemas needed to be loaded in the model's initial system prompt, and changing the tools list in the middle of a session was busting the cache. Any model can now overcome that with a Tool Search tool implementation

you can actually invoke an MCP App by name in both Codex and Claude using the @ handle

MCP context bloat is a solved problem since at least February. Both OpenAI and Anthropic support Client-side MCP tool search, which makes MCP context loading as efficient as the Skills one (progressive discovery).

Code mode is great but not needed anymore in 95% of use-cases.

- CLI tools don't have standardized auth, nor do they have granular tool permissions. MCP does

- CLI tools need to access your secrets in your .env. With MCP the model never sees the secrets and refresh tokens.

- CLI tools don't have auditing and telemetry. MCP provides all this for free.

- CLI tools imply full bash access, a nightmare in terms of security and very costly if you have to spin up a machine for every request for billions of users.

- etc

Models benchmarks start to get saturated again!