← Back to context

Comment by mooreds

11 hours ago

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.

9 comments

mooreds

Reply
rhipitr  7 hours ago

Isn’t tool drift/version also a benefit? Especially in scenarios where the use must be standardized and up to date?

debarshri  10 hours ago

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.

[1] https://adaptive.live

  • mooreds  8 hours ago

    > you can technically do with tools too

    By tools, do you mean skills? Or do I misunderstand you?

    Thanks for sharing your solution. I clicked around and the information on your site is sparse. The postgresql page[0] doesn't really illustrate how your system works; just says that it does.

    Regardless, there's a big difference between a proprietary way to inject skills and MCP, a standardized way to control access and deploy AI compatible logic.

    0: https://adaptive.live/integrations/postgresql

    • debarshri  8 hours ago

      Apologies about the sparse information. We’re preparing for a launch. Thought this would be a great place to make the comment. It is indeed a combination of tools and skills.

      Your argument is fair but yea, we are seeing adoption because tools often map to users mental model of how they want to use the agent.

      3 replies →