What's this about?
Gergely Orosz argued that vendors are misreading the moment: he already has one or two agents he likes, and unless you are a frontier lab he does not want yours. What he wants is an MCP interface so he can connect his agent to your service. It drew 4,432 likes and dotey made the same argument independently in Chinese.
What exactly is the distinction?
"Your agent" means a chat assistant built into a vendor's product, which only works inside that product. "An MCP interface" means the vendor exposes its capabilities as tools any assistant can call, so the user's own agent orchestrates across every service at once. The first makes the vendor the destination; the second makes them a component.
What's the community saying?
4,432 likes, plus independent agreement in the Chinese-language community
- Widespread agreement that every product shipping its own chatbot is the current version of every product shipping its own mobile app.
- dotey's formulation: everyone has two or three agents they actually use, so services should ship an MCP server or a CLI and stop building assistants.
- The implicit commercial tension — being a tool rather than a destination is a much weaker position, which is why vendors resist it.