We don't need SDKs, they publish API docs.

We don't need packages or functions, we can just write the code ourselves, every time it's needed.

We don't need compilers, the computer understands assembly already.

It's a mismatch of use - MCP isn't about telling the LLM about the APIs. It's also about encapsulating and simplifying them so the LLM isn't manually figuring them out every single time from scratch.

OpenAPI specs provide everything the LLM needs to understand an API. And if it can be simplified for the LLM while retaining functionality, why not simplify the API altogether, instead of implementing yet another entry point into the application? Just so nobody has to sit down for longer than the duration of a TikTok and design their API properly?

> That allows already for self discovery etc.

The problem is usually not with listing the APIs. Almost all services have OpenAPI specs, and you can (often too) complain about lack of documentation.

Orchestrating these APIs is the annoying "fuzzy" challenge. Imagine you have a VM service, and you provide a set of APIs. Someone comes asking "How do I create a copy of a VM we have in the US region to EU region but with half the CPU/RAM?"

You might point to your OpenAPI spec and say you can:

    var s1 = takeSnapshot(vm1);
    var s2 = copySnapshot(s1, 'EU');

    var vm2 = createVmFromSnapShopt(s2, sizeOverride).

Ok... but is there a makeACopyOfVmWithHalfCPUAndHalfMemoryInEurope(vm1) API? I don't want to copy that code. In 3 months it'll break because `vm1` is of a type that can't be snapshoted and you'll tell me that I should check `vm1.snapshotable`, or that the new size is invalid in the new region because I should be calling `isSizeAvailable()`

If this were an MCP, then it would either orchestrate these APIs "correctly" for me checking as corner cases as possible as (presumably from examples it saw on github). When it misses, it's "oh well, even AI couldn't get it. We can all blame AI everybody" As oppose to when a Human misses and someone is like "how amateurish is the implementation that you're not checking if the vm is `snapshotable` or not?

the value is being able to extend the internal website mcp, so it can grab the data i need.

i can script across a billion systems that i would never go through the work of getting auth/setting up all the service calls and workflows for.

the mcp doesnt need any new permissions, its just what ive got website access to