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 .

> LLM Can call tools without MCP 100% fine.

but can the LLM host UI ask me for permission (in an outside-of-LLM domain) if the LLM wants to call API foo.bar ?

Thats all part of how you code the LLMHost Backend and Frontend. I build several MCP and MCP-Less tool calling agents using autogen and they can ask the user permission. That is nothing to do with MCP at all.

Look into AutoGen by microsoft or if you want more basic , learn how tool calling in LLMs work.