https://video.ut0pia.org/videos/watch/cae4dd4b-91e8-496a-b44c-418b9825f2e2 The best MCP server is the one you didn't have to build. At Cloudflare we have a lot of products. Our REST OpenAPI spec is over 2.3 million tokens. When teams started building MCP servers, they did what everyone does: cherry-picked important endpoints for their product, wrote some tool definitions and shipped a separate service that covered a small fraction of their API. This was driven by a fundamental context limit of the end users' agent. And tools use a bunch of context just to describe themselves. MCP felt like a Mega Context Problem (and a separate service to maintain). I think we got it all wrong. The context limit is not an MCP problem. It's an agent problem. Tools should probably be discovered on demand and clients are coming around to this. But maybe we can also do it on the server? CLIs get this for free, self-discoverable and documented by design. APIs just need a little help. This talk will cover some of the techniques we've been exploring at Cloudflare, such as codemode and tool search, to make complete APIs accessible to agents through MCP. I'll also cover some of the work we are doing with the MCP Typescript SDK to make stateless servers the default. Speaker info: https://github.com/mattzcarey, https://www.linkedin.com/in/mattzcarey/, https://x.com/mattzcarey Sun, 26 Apr 2026 11:50:26 GMT https://validator.w3.org/feed/docs/rss2.html PeerTube - https://video.ut0pia.org https://video.ut0pia.org/lazy-static/avatars/0287a09a-aae7-4840-9843-b416426e7046.webp https://video.ut0pia.org/videos/watch/cae4dd4b-91e8-496a-b44c-418b9825f2e2 All rights reserved, unless otherwise specified in the terms specified at https://video.ut0pia.org/about and potential licenses granted by each content's rightholder.