I run the team at OpenAI that's responsible for the ChatGPT App Store, Codex plugins, and all things MCP.
The thing that all these "MCP is dead" posts are missing is that whether or not MCP is used as a transport protocol is actually completely irrelevant.
The reason MCP isn't dead is because practically ~every company on the planet is building an MCP server. I know this because we interact with all of them. Most of these companies don't have a CLI. Many of these companies don't even have an external API! And yet, they're all building MCP servers.
And that's why MCP is not only not dead, but more important than ever.
Maybe we will turn every MCP server into a CLI under the hood. Maybe we'll use code mode. Maybe we'll implement tool search.
All of those are just implementation details to the much more important point: our AI agents are getting access to services they otherwise would never have had access to.[0] That's what matters.
So, is MCP dead as a direct communication layer for models to speak to? Maybe, maybe not. Is MCP dead as a protocol? Hell no, couldn't be further from the truth.
[0]: Although I will say the Codex app's computer & browser use features have made this statement a lot weaker than it used to be. If you haven't tried them yet—they're mindblowing.
It's interesting that he signs off with "So long, and thanks for all the fish," which is a quote from The Hitchhiker’s Guide to the Galaxy:
Just before the Vogons demolish Earth to make way for a hyperspace bypass, the dolphins, knowing what’s coming, leave the planet and their farewell message is “So long, and thanks for all the fish.”
I've been doing this for years with my meetings and I wish Google Calendar had it built in. I have to keep manually adjusting start times and it's a pain.
Oh man, I got excited to use this with our kids, but then saw that it requires a " mobile device management (MDM) solution and Managed Apple IDs." I hope they consider the family use case in the future.
Love seeing more innovation in this space! I know Oleg (former Webflow eng) has been working on https://webstudio.is for a while; also open-source and visual editing for React apps. How does Onlook compare?
Absolutely, if you're building a GraphQL server, parsing is almost certainly not your bottleneck. Stellate is effectively a GraphQL CDN, so for us, it is.
Our request flow effectively boils down to:
1. Parsing a GraphQL query to assess which types and fields are within it
2. Matching the configured cache rules to those types and fields
3. Caching partial results accordingly
So, for our specific use case, parsing is one of the main things our edge gateway does, and reducing overhead there allowed us to significantly improve our overall performance.
> Default GQL encoding is redundant and we care a lot about limiting size because many of our customers have low bandwidth
I'd love to know how you ended up combating this! I'm assuming something like graphql-crunch[0] or graphql-deduplicator[1], but I'd love to know what worked well in practice.
I feel like this title is misleading compared to the original article. (cc @dang) Fly.io without cold starts (which is a one-line configuration change) is 2x faster than Cloudflare Workers.
The thing that all these "MCP is dead" posts are missing is that whether or not MCP is used as a transport protocol is actually completely irrelevant.
The reason MCP isn't dead is because practically ~every company on the planet is building an MCP server. I know this because we interact with all of them. Most of these companies don't have a CLI. Many of these companies don't even have an external API! And yet, they're all building MCP servers.
And that's why MCP is not only not dead, but more important than ever.
Maybe we will turn every MCP server into a CLI under the hood. Maybe we'll use code mode. Maybe we'll implement tool search.
All of those are just implementation details to the much more important point: our AI agents are getting access to services they otherwise would never have had access to.[0] That's what matters.
So, is MCP dead as a direct communication layer for models to speak to? Maybe, maybe not. Is MCP dead as a protocol? Hell no, couldn't be further from the truth.
[0]: Although I will say the Codex app's computer & browser use features have made this statement a lot weaker than it used to be. If you haven't tried them yet—they're mindblowing.