FastMCP 3.0 Release Webinar

38:12 Q&A starts 38:53 Per-tool authorization 39:09 Unmounting servers 40:58 FastMCP in Frontier 42:10 Registry support 44:04 Code review workflow & AI in the process 48:08 Prefab native app support 50:44 Code mode & sandboxing with Monty 53:16 A2A protocol thoughts 55:29 MCP apps & external URLs 57:17 Background tasks & closing … ... {ts:395} is that incremental features took longer and longer and longer to add on because the surface area of worrying about {ts:402} interrupting or disrupting or compliance with other features in the system. It's a framework. Everything has to work {ts:409} together. And if everything shares its own code path, well, all of a sudden, introducing a new code path and trying … {ts:465} And I was like, "Oh, this is great. ... … So, mounting servers in open API, which is the {ts:1204} feature that we love to hate. Um uh so many people are building MCP servers by converting open API specs uh and then {ts:1212} they end up with a really bad MCP server because it's a different type of API uh and then they blame MCP and that gets {ts:1219} really frustrating after a while and so I had to write this blog post telling people to stop using this feature. Uh {ts:1224} nobody has stopped using it. They use it a lot. um it's disproportionately um issues opened and enhancements requested {ts:1231} and so happily the open API converter is now implemented as a provider which again lets it be compatible with