Comment by fnordsensei
4 days ago
As a provider, I can add a tool or change instructions on my MCP server, and you'll get it on your next connection, sometimes even mid-session.
With a skill, updates depend on whatever channel delivered it to you. Whichever channel that is, it's out of my hands as a provider.
So, MCP solves the problem of coordinated distribution of updates to a larger subscriber base. Think inside of a company, for example. I don't have to go around and tell people to `git pull` their skills folder.
How is this different from a skill giving you are a URL to another skill file where you can find an up to date list of everything that is available?
Because why should you have to load "here's how to update this skill!" information into the context window every time you use it? Would you expect the agent to go to that URL and look for more recent skill files every time you use it? Is this a real question?
Versus having an agent read MCP config and fetch the existing tools every time it wants to use the MCP? It's duplicate functionality.
2 replies →
[dead]