"[T]he vast majority of MCP servers are a waste of time. And that’s normal because the MCP spec is only months old. People jump into it, and they start building for MCP without really thinking it through or understanding what it should be.
The vast majority of MCPs that you can see now are reflections of APIs. I think that’s a complete waste of time. This might be offensive, but let’s take Kubernetes. As an example, Kubernetes is an API-driven platform of sorts. Now let’s say you have a Kubernetes MCP server that basically allows you to get resources, to describe resources, and to see the logs and so on and so forth. They’re basically reflections of the Kubernetes API, just as kubectl is a reflection of the Kubernetes API.
Now, does an AI agent really need that MCP server? Absolutely not. It’s perfectly capable of using kubectl directly. And even if there weren’t a kubectl CLI, it’s perfectly capable of talking to the API as is. And it’s not hard for an AI backed by an agent to execute the URL commands to go to some API, and effectively do the same thing that that MCP server is doing.
What we need is MCPs that are actually providing additional value around user intents. Instead of having a Kubernetes MCP server that is a reflection of its API, have a Kubernetes MCP that will have certain logic or workflow or this or that, that will help you combine resources to get an application up and running. So, something beyond just a one-to-one reflection of an API."
https://nordicapis.com/why-internal-developer-platforms-need-apis/
#APIs #APIFirst #MCPs #AI #GenerativeAI #AIAgents