Prefect Rebuilds FastMCP 3.0 to Power 70% of all MCP Servers
Prefect ships FastMCP 3.0, a ground-up architectural redesign of the most widely used MCP framework, now powering 70% of all MCP servers
Takeaways
- FastMCP 3.0 ships: Prefect releases a ground-up architectural redesign of the most widely used MCP framework, downloaded a million times a day.
- New architecture: Everything is now composed from three primitives — Components, Providers, and Transforms — replacing a tangle of independent subsystems.
- Five built-in providers: LocalProvider, FileSystemProvider (with hot-reload), OpenAPIProvider, ProxyProvider, and SkillsProvider for serving agent skills over MCP.
- Major new features: Per-component OAuth authorization, component versioning, session-scoped state with Redis backend, native OpenTelemetry tracing, and background tasks.
- Minimal breaking changes:
@mcp.toolstill works; main changes are async state methods and removal of theenabledparameter on components. - Enterprise layer: Prefect Horizon adds SSO, tool-level RBAC, audit logs, and a private MCP registry on top of the open-source framework. Docs | GitHub
FastMCP, the Python framework powering the majority of the MCP ecosystem, just shipped its largest release. Prefect's Jeremiah Lowin announced FastMCP 3.0 as a complete architectural redesign: a rethinking of how MCP servers are built, not a feature drop. The release also moves the project from the personal jlowin/fastmcp repo to PrefectHQ/fastmcp, making it an officially Prefect-backed product.
What FastMCP already was
FastMCP 1.0 proved the concept so well that Anthropic made it the foundation of the official MCP Python SDK. FastMCP 2.0 introduced the infrastructure needed to build a real server ecosystem, arriving alongside the MCP hype wave. Today, FastMCP is downloaded a million times a day, with some version of it powering 70% of all MCP servers.
As the framework grew, v2 became reactive: new infrastructure bolted on to match demand, features hacked in so developers wouldn't have to build them themselves. The result was a collection of independent subsystems, each with its own code, its own mental model, and its own edge cases.
One architecture for everything
FastMCP 3 is built around a single question: what if all of these features are just different combinations of the same primitives? The answer is a three-concept architecture:
- Components are the atoms: tools, resources, prompts. What clients actually interact with.
- Providers answer "where do components come from?" A provider is anything that can list components and retrieve them by name. Your decorated functions are a provider. A directory of files is a provider. A remote MCP server is a provider. An OpenAPI spec is a provider. A FastMCP server is itself a provider, which means you can nest servers inside servers, indefinitely.
- Transforms are middleware for the component pipeline. They intercept the flow of components from providers to clients and can modify what passes through. Rename a tool, add a namespace prefix, filter by version, hide components by tag: these are all transforms. Transforms compose by stacking, each one processing the output of the previous.