Genuine question, why can't this be done via an API that the agents call? there are already established ways to call APIs on behalf of the user. Seems to me that the agent is loading a web app just to be able to access it's apis, what am i missng?
Yeah, we could have just standarized around a path to api specs. Maybe .well-known/openapi.yaml
Maybe it's cynical, but the best reason I can come up with is that 'established common url for api specs' does not sound nearly as cool on a CV or when talking about the next promotion as 'invented WebMCP'. And for those implementing it on their websites 'we implemented WebMCP' is again much more 'AI-first' than 'we uploaded our API specs'.
Yeah, we could have just standarized around a path to api specs. Maybe .well-known/openapi.yaml
Maybe it's cynical, but the best reason I can come up with is that 'established common url for api specs' does not sound nearly as cool on a CV or when talking about the next promotion as 'invented WebMCP'. And for those implementing it on their websites 'we implemented WebMCP' is again much more 'AI-first' than 'we uploaded our API specs'.