4 ms·
>It's JSON-RPC, with some descriptors. That's not even true. It defines the lifecycle of tool calling. JSON-RPC with some descriptors would have been fine and
by whoknowsidont 11mo ago
>It's JSON-RPC, with some descriptors.
That's not even true. It defines the lifecycle of tool calling.
JSON-RPC with some descriptors would have been fine and amazing.
- frumplestlatz 11mo agoI’m struggling to understand where you’re coming from. Your hate for MCP seems grossly outsized relative to what it actually is.
- paulddraper 11mo agoThis comment is unhinged. https://modelcontextprotocol.info/docs/concepts/transports/ https://modelcontextprotocol.info/docs/concepts/transports/
- whoknowsidont 11mo agoYou linked to one part of the spec and just wanted to ignore everything else? That's fine, but then you wouldn't be obeying the standard and wouldn't be an "MCP." So, are you agreeing with me? Respectfully I think I've engaged with you before and you just seem generally confused about nuanced concepts.
- didibus 11mo agoI'm open mindedly hoping you'll be more specific in what about the protocol you find problematic? The base protocol is just JSON-RPC, and then you have to implement initialize. Everything else is optional.