gmays1d ago

I still prefer MCP over skills

https://david.coffee/i-still-prefer-mcp-over-skills/

I Still Prefer MCP Over Skills

Why I believe the Model Context Protocol (MCP) is a better architectural pattern than the emerging “Skills” trend for LLM tool integration.

David Mohl
Show threadplandis1d ago

I could not agree any less with the author. I don’t want APIs, I want agents to use the same CLI tooling I already use that is locally available. If my agents are using CLI tooling anyways there is no need to add an extra layer via MCP.

I don’t want remote MCP calls, I don’t even want remote models but that’s cost prohibitive.

If I need to call an API, a skill with existing CLI tooling is more than capable.

Show threadwoeirua1d 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.
Show threadhansonkd
idk, just have a standard internet request tool that skills can describe endpoints to. like you could mock `curl` even for the same CLI feel
Apr 10 at 3:26amWeb
Show threadwoeirua1d ago
Now you’ve replicated MCP but with extra steps and it’s harder to debug.