gofastmcp.com
FastMCP Updates
Excerpt
## FastMCP 2.14.6: $Ref Dead Redemption v2.14.4 backported `dereference_refs()` but never wired it into the tool schema pipeline — `$ref` and `$defs` were still sent to MCP clients. Now fixed: schemas are fully inlined before reaching clients. ... Fixes a memory leak in the memory:// docket broker where cancelled tasks accumulated instead of being cleaned up. Bumps pydocket to ≥0.17.2. ... Fixes a fresh install bug where the packaging library was missing as a direct dependency, plus backports $ref dereferencing in tool schemas and a task capabilities location fix. FastMCP 2.14.3 ... ## FastMCP 2.14.3: Time After Timeout Sometimes five seconds just isn’t enough. This release fixes an HTTP transport bug that was cutting connections short, along with OAuth and Redis fixes, better ASGI support, and CLI update notifications so you never miss a beat. FastMCP 2.14.2 ... December 31, 2025 ... FastMCP 2.14.2 brings a wave of community contributions safely into the 2.x line. A variety of important fixes backported from 3.0 work improve OpenAPI 3.1 compatibility, MCP spec compliance for output schemas and elicitation, and correct a subtle base_url fallback issue. The CLI now gently reminds you that FastMCP 3.0 is on the horizon. … ... FastMCP 2.14 begins adopting the MCP 2025-11-25 specification, introducing protocol-native background tasks that enable long-running operations to report progress without blocking clients.⏳ **Background Tasks (SEP-1686)** let you add `task=True` to any async tool decorator. Powered by Docket for enterprise task scheduling—in-memory backends work out-of-the-box, Redis enables persistence and horizontal scaling. … ## FastMCP 2.13.1: Heavy Meta Introduces meta parameter support for `ToolResult`, enabling tools to return supplementary metadata alongside results for patterns like OpenAI’s Apps SDK.🏷️ **Meta parameters** let tools return supplementary metadata alongside results.🔐 **New auth providers** for OCI and Supabase, plus custom token verifiers with DebugTokenVerifier for development.🔒 **Security fixes** for CVE-2025-61920 and safer Cursor deeplink URL validation on Windows. … The new consent screen prevents confused deputy and authorization bypass attacks discovered in earlier versions, while the OAuth proxy now issues its own tokens with automatic key derivation. RFC 7662 token introspection support enables enterprise auth flows, and path prefix mounting enables OAuth-protected servers to integrate into existing web applications. FastMCP now supports out-of-the-box authentication with WorkOS and AuthKit, GitHub, Google, Azure (Entra ID), AWS Cognito, Auth0, Descope, Scalekit, JWTs, and RFC 7662 token introspection. … ## FastMCP 2.12.5: Safety Pin Pins MCP SDK version below 1.17 to ensure the `.well-known` payload appears in the expected location when using FastMCP auth providers with composite applications. FastMCP 2.12.4 ... ## FastMCP 2.12.2: Perchance to Stream Hotfix for streamable-http transport validation in fastmcp.json configuration files, resolving a parsing error when CLI arguments were merged against the configuration spec. FastMCP 2.12.1 ... FastMCP 2.10 achieves full compliance with the 6/18/2025 MCP specification update, introducing powerful new communication patterns.💬 **Elicitation Support** enables dynamic server-client communication and “human-in-the-loop” workflows, allowing servers to request additional information during execution.📊 **Output Schemas** provide structured outputs for tools, making results more predictable and easier to parse programmatically.
Source URL
https://gofastmcp.com/v2/updatesRelated Pain Points
Memory leak in FastMCP memory:// transport broker
7The FastMCP memory:// docket broker accumulates cancelled tasks instead of cleaning them up, causing a memory leak in long-running servers.
$ref and $defs in tool schemas not dereferenced before sending
6Tool schemas with JSON Schema references ($ref, $defs) were not being inlined before being sent to MCP clients, violating spec requirements and causing client incompatibilities.
HTTP transport connection timeout too short (5 seconds)
6The HTTP transport was configured with a 5-second timeout that was cutting connections short for operations that needed more time to complete.