Kind of an interesting twist in IT history: Did it need the advent of AI Agents
Kind of an interesting twist in IT history: Did it need the advent of AI Agents to drive developer friendly, standardized and discoverable interfaces to systems?
Recently Model Context Protocol (MCP) got a lot of attention and traction. While this is good and exciting thing, I was wondering why this is actual needed? In a perfect & developer friendly world, it shouldn’t need another protocol just for agents, does it? AI should easily be able to use the existing interfaces, which have been built for convenience of human developers, no?
In Martin Keen’s video “MCP vs API: Simplifying AI Agent Integration with External Data”[1] you find a very good overview and comparison of MCP and APIs. Highly recommended to watch!
Still interesting to witness those things like HATEOAS (Hypermedia as the Engine of Application State), hypermedia types like siren, HAL and others, consistent & good API specifications, e.g. based on OpenAPI standard, and providing good sample client implementations as part of API provider deliverables never really got traction. In my experience both business stakeholders and developers rarely saw the value in this. Too much extra effort, not direct business value, …. Eventually ending up with developers taking on the integration efforts required to integrate systems. Same effort spent over and over again. Cost not being accounted for.
Now this seems to change. Capability providers happily invest into MCP server implementation to be part of the Agentic AI future. This is good, but maybe we should have done that already in a pre-AI Agent world?
Note that we might run into a cyclic dependency here as Martin also points out in his video, today’s implementations of MCP servers are just abstractions of existing APIs, which all the shortcoming above. But here AI system will be great support for developers for their MCP implementations.
Just a curiosity and point of view developed during my morning jog earlier today -what is your take on this?
Cross-posted to LinkedIn