| ▲ | s0ulf3re 15 hours ago | |
I’ve always felt like MCP is way better suited towards consumer usage rather than development environments. Like, yeah, MCP uses a lot of a context window, is more complex than it should be in structure, and it isn’t nearly as easy for models to call upon as a command line tool would be. But I believe that it’s also the most consumer friendly option available right now. It’s much easier for users to find what exactly a model can do with your app over it compared to building a skill that would work with it since clients can display every tool available to the user. There’s also no need for the model to setup any environment since it’s essentially just writing out a function, which saves time since there’s no need to setup as many virtual machine instructions. It obviously isn’t as useful in development environments where a higher level of risk can be accepted since changes can always be rolled back in the repository. If I recall correctly, there’s even a whole system for MCP being built, so it can actually show responses in a GUI much like Siri and the Google Assistant can. | ||
| ▲ | CharlieDigital 15 hours ago | parent [-] | |
That's MCP progress spec: https://modelcontextprotocol.io/specification/2025-11-25/bas... | ||