> This problem is best solved by the use of Skills which can contain instructions for both CLIs and APIs

You've just reversed the context benefits because the content of the skill...goes into context.

    > ...you can get the same benefits with a traditional centralized proxy as well. MCP doesn't inherently grant you any of those benefits. 

You've just rebuilt MCP...but bespoke, unstructured, and does not plug into industry tooling. MCP prompts are activated as `/` (slash) commands. MCP resources are activated as `@` (at) references. You can't do this with a proxy.

See the three .gifs at the end of the post to see how clients use MCP prompts and resources and definitely check the specification for these two.