Comment by troupo

> 1) MCP does more than just make an API call

It literally does that. What MCP calls a "tool call" is literally an API call (well, technically an RPC call since it's just JSON-RPC underneath).

But that's beside the point. Your original claim was this:

--- start quote ---

The only way you can connect different applications together are "integrations" (tightly coupling your app into the bespoke API of another app).

--- end quote ---

1. The MCP doesn't solve that. Every MCP server you connect to will expose their own bespoke API (aka tools) incompatible with anything else, in data formats incompatible with anything else.

2. No idea what SearXNG is, but if you used Swagger/OpenAPI or GraphQL you could easily have provided a standard way to discover what your API offers, and ways of calling that API

> You'd need to add extra code to SearXNG

You literally added extra code to SearXNG to expose an MCP server.

> GraphQL does not have any of the AI-specific features in it

Neither does MCP. Just because they invented new cute terms for JSON-RPC doesn't make it any more suitable for AI than literally any other protocol. And don't forget the idiocy of using a one-way communication protocol for two-way communication.

MCP re-invented SOAP, badly, with none of the advantages, and most of the disadvantages