WebMCP is mediated by the browser/page & has the full context of the user's active page/session available to it.
Websites that do offer real APIs usually have them as fairly separate things from the web's interface. So there's this big usability gap, where what you do on the API doesn't show up clearly on the web. If the user is just hitting API endpoints unofficially, it can create even worse unexpected split brain problems!
WebMCP offers something new: programmatic control endpoints that work well with what the user is actually seeing. A carefully crafted API can offer that, but this seamless interoperation of browsing and webmcp programmatic control is a novel very low impedance tie together that I find greatly promising for users, in a way that APIs never were.
And the starting point is far far less technical, which again just reduces that impedance mismatch that is so daunting about APIs.
alt Hacker News
WebMCP is mediated by the browser/page & has the full context of the user's active page/session available to it.
Websites that do offer real APIs usually have them as fairly separate things from the web's interface. So there's this big usability gap, where what you do on the API doesn't show up clearly on the web. If the user is just hitting API endpoints unofficially, it can create even worse unexpected split brain problems!
WebMCP offers something new: programmatic control endpoints that work well with what the user is actually seeing. A carefully crafted API can offer that, but this seamless interoperation of browsing and webmcp programmatic control is a novel very low impedance tie together that I find greatly promising for users, in a way that APIs never were.
And the starting point is far far less technical, which again just reduces that impedance mismatch that is so daunting about APIs.