MCP is dead?
441–444 of 444 posts
Re: MCP is dead?
#442Was this written by AI? MCP is essentially just JSON RPC with a few special fields that must be included. I have reservations about JSON RPC, but there needs to be some 'service discovery' layer for LLMs to interface with. It needs to be available in places like websites, desktop applications, backend services, etc. The CLI is only one place that these systems interface with. Whatever you replace MCP with will be in…
Re: MCP is dead?
#443has anybody ever use the prompt templates in practice? for what it's worth, these protocols are a product of their time, and unfortunately people lose patience with seeing it through in practice.
in the end it is all text. things are overengineered regardless, but at least this allowed reuse across projects.
Re: MCP is dead?
#444Earlier quoted context omitted.
How is the user installing the CLIs? Proprietary app store for each chat app?
I didn't mean that users would install them. I meant that if mcp and AI agents continue being popular, then Google and Apple could choose to provide apps with cli sandboxes with the proper permissions. It is a big change, but I just didn't understand the "never"; we've had bigger changes.
Of course anything is possible, I just don't think that people advocating for MCP's death have really thought through these problems, and are mostly focused on the desktop productivity use-cases.