MCP is a fad. The real thing to standardize upon is the OpenAI API, which is the actual thing that calls tools (which is literally OpenAI's job to do, but they don't care).

Reply to this note

Please Login to reply.

Discussion

So many services are OpenAI API compatible that it's already a standard, someone just needs to spec it

But if OpenAPI doesn't spec it and support it they can just change the API and rug everyone. Surely they would never...

Too late. It's already the industry standard, but like the other guy said it needs to be spec'd.

do you want xkcd 927? because that's how you get xkcd 927

There are 0 standards

that's just 14 less than the comic

I dont agree. OpenAI tool calling works, mcp is a different thing thats supposed to add tools to a frontend. Especially in the open source space thats important. We aren't going to bring every tool you may want for you, that would be crazy. At the backend we speak openai tool calls (and in our case soon KoboldAI Tool Calls as we are working on adding it to our UI).

A vscode extention may want to be able to execute certain things on nostr for example. You can make a MCP extention for the nostr communication. Then, all UI's capable of using MCP get that tool if hooked up to it, and they then forward the presence of this tool call to the LLM API server.

Its actually the frontend doing the translation between MCP servers and the LLM server. And this allows you to have internal tools with external providers without needing to give that LLM provider access to your datacenter.