4 ms·
Ok, but there are still many environments where an LLM will not have access to a CLI. In those situations, skills calling CLI tools to hook into APIs are DOA.
by woeirua 6mo ago
Ok, but there are still many environments where an LLM will not have access to a CLI. In those situations, skills calling CLI tools to hook into APIs are DOA.
- hansonkd 6mo agoidk, just have a standard internet request tool that skills can describe endpoints to. like you could mock `curl` even for the same CLI feel
- yawnxyz 6mo agoskills can have code bundled with them, including MCP code
- egeozcan 6mo agoWhat are the advantages of using an environment that doesn't have access to a CLI, only having to run/maintain your own server, or pay someone else to maintain that server, so AI has access to tools? Can't you just use AI in the said server?
- daemonologist 6mo agoObvious example is a corporate chatbot (if it's using tools, probably for internal use). Non-technical users might be accessing it from a phone or locked-down corporate device, and you probably don't want to run a CLI in a sandbox somewhere for every session, so you'd like the LLM to interface with some kind of API instead. Although, I think MCP is not really appropriate for this either. (And frankly I don't think chatbots make for good UX, but management sure likes them.)
- nostrebored 6mo agoWhy are they not calling APIs directly with strictly defined inputs and outputs like every other internal application? The story for MCP just makes no sense, especially in an enterprise.
- ok_dad 6mo agoMCP is an API with strictly defined inputs and outputs.
- nostrebored 6mo agoThis is obviously not what it is. If I give you APIGW would you be able to implement an MCP server with full functionality without a large amount of middleware?
- notpushkin 6mo agoSorry, could you rephrase that?