If you serve many environments you don’t get to bet on what protocol wins. You serve the way each consumer can actually consume This is why deBridge has MCP, CLI, SDK, RestAPI, OAS, swagger, curl snippets, docs, skills - because our consumers aren’t the same person.
deAlex
@AlexSmirnov
03-12
APIs/SDKs/CLIs are perfect if your consumer has a runtime and an interpreter, but a significant share of LLM clients don’t.
MCP extends the ones that can’t be harnessed any other way. Many LLM-native surfaces don’t execute code, MCP tool definitions are their native tongue. x.com/morganlinton/s…
From Twitter
Disclaimer: The content above is only the author's opinion which does not represent any position of Followin, and is not intended as, and shall not be understood or construed as, investment advice from Followin.
Like
Add to Favorites
Comments
Share
Relevant content
