3 ms·

I don't disagree, but the first sentence of your post happens to be true for very many specs/protocols I know of and have implemented in the past. And it is not

I don't disagree, but the first sentence of your post happens to be true for very many specs/protocols I know of and have implemented in the past. And it is not just communication protocols. Take PDF for example. The world practically runs on it, yet the file format is horrid. The real standard seems to be that standards are bloated by default.

Spivak 1y ago
Right but MCP is a brand new protocol which is at its core JSON-RPC formatted messages and a few verbs. It doesn't actually do much. The main things are tool definitions which is just a JSON schema describing a function call and resources which a is a wisp of a filesystem.
- tomashubelbauer 1y ago
  Fair, thought I have a feeling MCP will actually grow to do much more. I wouldn't disagree with the sentiment that it is too bloated too soon, but I also feel like it is destined to be bloated, because the technology it is targeting is sort of a moving target itself. Of course with proper versioning, this is easeable, deprecate stuff that turned out to be the wrong turn and cut major versions or introduce extensions to the protocol when new stuff is on the scene, but then you're liable to find yourself in an XMPP-style situation where no one implements the standard and extensions wholly, because it is so complex.