This all starting to look like autonomous driving. We are nowhere near solving it but everybody acts like it's here.

Can someone link to this supposed toaster with DP-alt mode? That supposedly runs on 240W? (Max PD power)

I believe Microsoft's usual "Embrace, Expand, Extinguish" strategy is at work here. For system stability and security reasons, you wouldn't actually want agents to dynamically discover tools without proper governance. Alternatives like PydanitcAI are lost in this steady MCP noise maintained by Microsoft - their "Embrace" phase for MCP, declared during Build 2025 event. Anthropic released this open standard with weak tooling and no governance for the specs, making it easy for Microsoft to dominate.

The next step would be Microsoft attempting to make their registry the de facto choice for developers and extending with Windows-specific verbs.

Then, by controlling what's considered "secure", they can marginalize competitors.

Central to this article, the author asks: "What if you just... removed the AI part?" and suggests a world of possibilities if we do. I disagree.

MCP is a protocol based on meagre structure and a bulk of human language. Either you use a large-language model to "read" this language, or you get a human to do it. The first is "AI" and the latter is... not very impressive.

Agents (presumably) increase the demand for APIs and if those APIs as well as already existing APIs get exposed as MCPs then I can see it.

It is dependent on agents actually creating new demand for APIs and MCP being successful as a way to expose them.

I know this is nit-picky and not really relevant to the actual meat of the story, but a toaster (outside of a gag gift or gimmick) cannot run on USB-C since your typical toaster draws ~1kW and USB-C power spec tops out at 240W.

I wonder how this interoperability hype in the industry, induced by MCPs, will affect companies where the lack of interoperability is almost a moat.

I remember when I first interacted with Marketo and I was wondering why people even bother trying to use this tool just to learn that Marketo has the best integration with Salesforce and thus, it’s almost a certainty that as you scale you’ll get to use it.

Salesforce in particular, relies a lot on the vendor ecosystem built on a platform that is so painful to inter operate with.

I’m very curious to see what effect this will have to them.

MCP works for small, well defined actions (like examples in the article), but enterprise APIs can have hundreds/thousands of endpoints/schemas for different concepts and variations of operations.

For example how would you MCP Google Ads rpc API https://developers.google.com/google-ads/api/reference/rpc/v... so that LLM and user will understand that? Seems like we can't escape complexity.

Anyone else feel like this article was written with ChatGPT

If MCP gets used this way I see big trouble when people hardcode stuff and then the provider updates the endpoints. MCP does not have versions as the list-tools is a living document, you are supposed to fetch and read the current version. AI would be totally fine with it because it would be able to reason the change and adapt, but the hardcoded app is going to break badly.