comparing kubernetes to what amounts to a subdirectory of shell scripts and their man pages is... brave?

anon84873628 12 hours ago | parent | next [-]

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.

▲

throwaway290 9 hours ago | parent [-]

Are you saying nearly every product company uses MCP? What a stretch

▲

mrbungie 9 hours ago | parent | next [-]

Welcome to the era of complex relationships with the truth. People comparing MCP to k8s is only the beginning.

▲

anon84873628 9 hours ago | parent | next [-]

I'd say this thread is both comparing and contrasting them...

▲

lomase 7 hours ago | parent | prev [-]

Truth Has Died

	▲	otabdeveloper4 3 hours ago \| parent [-]
		Lemme ask an AI to double check that vibe.

▲

anon84873628 9 hours ago | parent | prev [-]

I meant to say every enterprise product

	▲	throwaway290 9 hours ago \| parent [-]
		It doesn't matter because only a minority of product companies worldwide (regardless enterprise or not) uses MCP. I'd bet only minority uses LLMs in general.

▲

mbreese 8 hours ago | parent | prev [-]

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.

	▲	yard2010 2 hours ago \| parent [-]
		Honest question, Claude can understand and call REST APIs with docs, what is the added value? Why should anyone wrap a REST API with another layer? What does it unlock?