MCP is eating the world

In some ways MCP is like the next evolution of API over HTTP.

We've exposed our APIs as SOAP endpoints. These were not well suited to web based clients, leading to the development of "RESTful" JSON endpoints. As web clients became more complex, GraphQL arose as a solution to some of the problems encountered. Maybe MCP is the next step.

I don't mean that MCP will supersede these protocols. My company exposes our endpoints as SOAP, REST, and GraphQL still as they fit different use cases and customer bases. We are piloting an MCP version to see how that goes now.

It is fun to work on something new and play with agents to see how they consume our endpoints in this form. I think there is a lot of potential.

Unecessary complication. LLM Can call tools without MCP 100% fine. You don't need a Stateful SSE JSORPC Meshedup server running APIs rebraneded as tools at somewhere on the cloud .

I think there's going to be a lot of places where you want the middleare that's only exposing a sub-set of apis. and the Ideas that you copy some URL, put it in your LLM Client, and then it magically gets all the tools/endpoints available to you, and you start interacting with it, simplifies the process greatly for a lot of users. No swagger, no http post, body vs params, etc....just play with with your prompt sentance until you get it to do what you want.

(edit: sorry, I responded to wrong thread.)