Because that would make too much sense, and MCP is trendy. Also probably more likely is people don't want to spend effort creating sensible http APIs, instead they like using frameworks like Next.js that strongly couple client and server together.
Jokes on them though if they want this to work, they'll have to add another API, but now on the client code and exposed through WebMCP.
Because that would make too much sense, and MCP is trendy. Also probably more likely is people don't want to spend effort creating sensible http APIs, instead they like using frameworks like Next.js that strongly couple client and server together.
Jokes on them though if they want this to work, they'll have to add another API, but now on the client code and exposed through WebMCP.
No idea, seems like a much better fit :shrug: