I think that this extension points out other benefits to MCP over skills:
* centralized control
* ease of use for employees
* auditing/compliance
* deployment model
It seems the state of the art for deploying skills is "copy this file and put it in this place" or "check out this repo and add a symlink" or "run this slash command to install the skill". (I'm not aware of any solution that pushes skills out.)These options are simple, but not as easy as this extension makes rollout of a new MCP server to an employee.
There's a new standard in progress for skills over MCP
https://modelcontextprotocol.io/community/working-groups/ski...
Isn’t tool drift/version also a benefit? Especially in scenarios where the use must be standardized and up to date?
All the points that you are mentioning, you can technically do with tools too. We do that at adaptive [1]. We are building privileges access stuff for agents, and it works. The usecases you are mentioning can be done with tools via our platform.
Claude CLI has plugins and plugin marketplaces that solve the problem you're describing.