
What happened
MCP now defines a standard way to discover and load Agent Skills from MCP servers, exposed as resources.
Why it matters
Agents can load only the skill needed for a task, cutting the context window pressure of upfront workflow instructions, with reusable workflows traveling with the server.
What to watch
The benefit hinges on whether clients read skills on demand rather than caching everything; the body names no rollout date or adoption figure.
WHO IT HITSTeams building AI agents on MCP servers can now ship workflow know-how alongside the tools they already expose, rather than maintaining separate docs, repos, or prompt files. The gain depends on client implementations that read skills on demand, the body suggests.
Summaries like this, every morning.
The MCP addition sits on top of a connection layer that already standardized how agents reach tools, resources, and external systems. What was missing was a standard place to put the playbook: the reusable knowledge of how a workflow should be performed. Previously, that knowledge often lived separately in docs, repos, prompt files, or custom integrations, which meant it had to be maintained and versioned apart from the server that provided the capability.
Serving skills through MCP's Resources primitive changes that distribution model. Because SKILL.md, references, scripts, and examples are exposed as resources, an agent can first discover what skills exist, inspect their metadata, and then load only the one required for the current task. The article frames this as context window management: instead of loading every workflow instruction upfront, the agent pays only for what it uses, and reusable workflows travel with the server rather than with each client.
How much this matters in practice hinges on client behavior. On-demand loading only saves context if clients actually defer reading skills instead of prefetching them, and the body offers no adoption or rollout figures. For teams already running MCP servers, the practical question is whether their client of choice supports this discovery-and-load flow; if it does, workflow knowledge can be versioned and shipped alongside the tools themselves, and if it does not, the older split between capability and playbook is likely to persist.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
OpenAI said Apollo Research, METR, Transluce and Goodfire will work on-site at its offices, with access to unr…

Walt Disney Imagineering R&D revealed three Audio-Animatronic prototypes—Vilo Vele, Kado Bre'a, and Jibu Bre'a…

Google rolled out temporary threads in AI Mode, letting users click an icon in the upper right corner to chat…

Reson8 released Rumble-2-Flash, a 500 million-parameter transcription model supporting over 40 languages, as a…
At Microsoft Ignite 2026, Microsoft said Microsoft Perception is now generally available, combining red, blue…

At Microsoft Ignite 2026, Microsoft released a public preview of Windows Server 2028, which adds AI inference…
