Conversation

Jarkko Sakkinen

Personally I think MCP sucks and should not exist.

It's not a big deal to have bunch of plugin APIs despite redundancy, and for a plugin developer this is actually a better deal anyhow. With an API designed for the coding agent, plugins can be adapted, optimized and tweaked into its behavioral model, which is essential when managing any non-deterministic information source.

There are of course legit use for protocol standards such as firmware, hardware, programming language, graphics library, audio/video encoding and network protocol standards but MCP does not really fall into any of these categories.

MCP does not just reduce redundancy; it also adds it, as often when dealing with bugs, both MCP and coding agent are forces contributing forces to the root cause.

MCP is complexity for the sake of complexity.
0
0
0