Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

FastMCP 4.2 serves skills from the server

Written November 16, 2026

FastMCP 4.2 holds one copy of a skill on the server and updates every agent that reads it. The 4.1 skills API is deprecated, removal in 4.3.

The FastMCP 4.2 release notes, dated November 13, 2026, change where a skill lives. Until now, a skill sat in a folder on each machine, so every agent kept its own copy and an update meant asking everyone to reinstall. In 4.2 the server holds one copy next to the tools the skill describes, and a deploy updates every agent that reads it. For a team that serves tools with FastMCP and keeps its skills in step with them, that removes a distribution chore that grew with every new machine.

Serving a skill takes a provider

The release notes give this sample for serving a skill from a directory:

from fastmcp import FastMCP, Skill
from fastmcp.skills.provider import SkillCatalogProvider

deploy = Skill.from_directory("skills/deploy")

mcp = FastMCP("Team Skills")
mcp.add_provider(SkillCatalogProvider([deploy]))

A SkillCatalogProvider serves a Skill built from a directory, alongside the server's tools. The skill and the tools it describes now travel together: change the skill on the server, deploy, and the next agent to read it gets the new version instead of whatever copy was installed on its machine weeks earlier.

That placement is the point of the change. A skill that describes a server's tools no longer travels separately from those tools, on a schedule set by whoever happened to install it on each machine. The server holds the one copy, and a client reads the skill from the server's current version, in the same place it already goes for the tools themselves.

How clients read a served skill

Any client can read a skill's files as ordinary resources, with no new protocol support needed. Clients that speak the experimental Skills extension, SEP-2640, also get skills/list, with a hashed manifest for each skill. The notes are plain that few hosts support the extension yet, so FastMCP's own client fills the gap: Client.read_skill() compares every file's size and digest, and to_directory() installs a skill into an agent's local skills folder. Skills also work with the rest of FastMCP. They are namespaced under mounts, pass through proxies, list across a ClientGroup, and respect AuthMiddleware, per the release notes. The FastMCP skills docs cover the details.

Before upgrading

That gives teams on the 4.1 API one release cycle to move. The old code does not break on 4.2 — it warns — but anything still on it when 4.3 lands will stop working, so the upgrade to 4.2 is the time to make the switch rather than a separate project later.

Limits and the rest of the release

The main limit is host support for the extension. The skills/list path with its hashed manifest depends on the experimental SEP-2640 extension, and few hosts speak it yet; until they do, the resource path and FastMCP's own client are how most agents will read served skills. Beyond skills, 4.2 lets dependencies be declared in the annotation, as in Annotated[dict, Depends(get_config)], so a parameter keeps its real type, and a dependency can own the tool argument it reads through CallArgument. The rest of the release is fixes across OpenAPI, proxies, auth, telemetry, and tasks.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Agent Skills has a neutral home — and still no security story