newreleases.io
jlowin/fastmcp v2.13.0 on GitHub - NewReleases.io
Excerpt
**"Cache Me If You Can"** represents a fundamental maturation of the framework. After months of community feedback on authentication and state management, this release delivers the infrastructure FastMCP needs to handle production workloads: persistent storage, response caching, and pragmatic OAuth improvements that reflect real-world deployment challenges. … `/api`, and MCP 1.17+ compliance with RFC 9728 ensures protocol compatibility. Combined with improved error handling and platform-aware token storage, OAuth is now production-ready and security-hardened for serious applications. FastMCP now supports out-of-the-box authentication with: **WorkOS**and **AuthKit** **GitHub** **Azure**(Entra ID) **AWS Cognito** **Auth0** **Descope** **Scalekit** **JWTs** **RFC 7662 token introspection** **Response Caching Middleware** dramatically improves performance for expensive operations. Cache tool and resource responses with configurable TTLs, reducing redundant API calls and speeding up repeated queries. **Server lifespans** provide proper initialization and cleanup hooks that run once per server instance instead of per client session. This fixes a long-standing source of confusion in the MCP SDK and enables proper resource management for database connections, background tasks, and other server-level state. Note: this is a breaking behavioral change if you were using the … ... - Azure (Entra) OAuth: Validate token against FastMCP app, not Graph. by @nbaju1 in #1891 - Default to FastMCP version when server version not specified by @jlowin in #2022 - Check if refresh_token is None by @Kyle-Dinh in #2025 … - Expose OAuth token management parameters across all providers by @jlowin in #2222 ... - Fix Azure scope mismatch causing MCP client validation errors by @jlowin in #2243 - Add exc_info=True to inspect command error logging by @aaazzam in #2232
Related Pain Points
Production-grade resource management and state persistence gaps in MCP
7MCP servers lack built-in support for production workloads including proper memory limits, concurrent request handling, rate limiting, health checks, persistent storage, and state management. Developers must manually implement these critical infrastructure concerns.
Enterprise Deployment Requirements Not Well-Defined
7Enterprises deploying MCP face a predictable set of problems including audit trails, SSO-integrated auth, gateway behavior, and configuration portability. These requirements are poorly defined and understood.