| ▲ | CSMastermind 2 hours ago | |
Was 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 a similar shape even if you specify a different communication protocol or different fields for tool discovery. | ||
| ▲ | bluegatty 2 hours ago | parent [-] | |
It's the way that it occupies the context relatively permanently, that it doesn't come along with nice install/uninstall or discovery etc. is the problem. 'Skills' should all be based on MCP, they should load on demand, be very easily manageable and discoverable by humans and by AI, and then it would work The scope was too narrow, given how it ended up being applied. If they layer something on top of it, it may yet be revived. | ||