Repository navigation
v0.10.0 — FastMCP removed
FastMCP support is removed. Deprecated in 0.9.0, it is gone in 0.10.0: every generated project is now an Official MCP SDK v2 project.
Breaking:
--framework=fastmcpnow exits with an error. Existing generated projects are unaffected — they pin their own dependencies and never depend on this CLI.
Why
FastMCP never migrated to MCP SDK v2. It still depends on the v1 @modelcontextprotocol/sdk, so FastMCP projects spoke the 2025-era protocol and shipped without the test suite SDK projects have had since 0.8.0. Keeping it meant a second set of templates that lagged on every axis this CLI cares about.
What changes
- One framework. Interactive mode no longer asks for a framework, or for the FastMCP-only stateless/stateful choice.
--frameworkstill parses.--framework=sdkkeeps working, so existing scripts don't break.--framework=fastmcpexits with a message explaining the removal and how to keep scaffolding FastMCP.- SDK projects are unchanged. Generated HTTP, stdio and OAuth projects are byte-identical to 0.9.0.
If you still need FastMCP
Pin the last release line that supports it:
npx @agentailor/create-mcp-server@0.9 --name=my-server --framework=fastmcpRelease pipeline
Releases are now published with npm trusted publishing (OIDC) rather than a long-lived token, and are staged: CI uploads the version, and it goes live only after a maintainer approves it with 2FA. Packages also carry signed provenance linking them to the GitHub Actions run that built them.
Upgrading
npx @agentailor/create-mcp-server@0.10.0Full changelog: v0.9.0...v0.10.0