People said the same thing about "APIs" 10-15 years ago when they were a craze. Everything had to be an API! Doesn't matter whether it made sense to not. It's going to change the world! We're going to have San Francisco events with microbrews for APIs! Everyone's going to publish API frameworks! Let me make api-blog-blog.blogger.blog!
Blah. Bay Area Tech regularly goes through these bursts of baseless enthusiasm for rehashes of existing technology. Is MCP useful? Yeah, probably. Is the current froth based on anything but SF-scene self-licking-ice-cream-code social cred? No.
> Bay Area Tech regularly goes through these bursts of baseless enthusiasm for rehashes of existing technology. Is MCP useful? Yeah, probably. Is the current froth based on anything but SF-scene self-licking-ice-cream-code social cred? No.
Thank you. You said what I was going to say. Another goose chase for something that's valuable, certainly, but being frothed up into some mythical sword in the stone.
It's ultimately just a way to say "hey, here's some extra context including some functions we have defined on our server that you can ask us to call."
Blah. Bay Area Tech regularly goes through these bursts of baseless enthusiasm for rehashes of existing technology. Is MCP useful? Yeah, probably. Is the current froth based on anything but SF-scene self-licking-ice-cream-code social cred? No.