comparing kubernetes to what amounts to a subdirectory of shell scripts and their man pages is... brave?
For what it's worth, I don't write MCP servers that are shell scripts. I have ones that are http servers that load data from a database. It's nothing really all that more exciting than a REST API with an MCP front end thrown on top.
Many people only use local MCP resources, which is fine... it provides access to your specific environment.
For me however, it's been great to be able to have a remote MCP HTTP server that responds to requests from more than just me. Or to make the entire chat server (with pre-configured remote MCP servers) accessible to a wider (company internal) audience.
Shell scripts written by nearly every product company out there.
There are lots of small and niche projects under the Linux Foundation. What matters for MCP right now is the vendor neutrality.