There's two use cases for WebMCP I've seen: 1. Enabling non API only products to work over MCP. An example of this is a design tool like @paper and how they have a ton of canvas rendering required 2. WebMCP enables just a single engineer to get a product accessible over MCP This is one of the most important things imo, as shipping a full MCP is significantly larger amount of work than reusing your existing auth and deployment While it's not the ideal solution, someone can ship it…