Skip to content

MCP: usability, abstraction, and scaling costs

So MCP's. I get it. I understand the Gimmick.
I like the usability of it, a lot.

But....

1. It's not a huge amount of value for the effort you have to put in in order to get it right.

2. It's not easy to secure these things. Any productivity gains you get, are lost when you realize that every endpoint needs permissions and roles on the other side, if you're going to do it safely. No way around that. If you're not doing it that way, you're wrong. And you will feel it later.

3. It's never EVER going to scale. It can't. If you stack these things the way people want to stack them... you're done. Good for small projects, you start to hit some real bottlenecks on medium sized ones.

4. It's loud. Lots of constant network chatter that doesn't need to be there.

5. It's too much abstraction. Ridiculous amounts of abstraction, where the only solution is more abstraction and aggregation of abstraction.

6. What people actually want, without realizing it, is FastAPI, which already existed. Does the main use case with no weird overhead, handles network discovery and auto-prompting, if you implement it properly. And it doesn't open up a billion rpc's and websockets, that you never needed in the first place.