insights
Practical thinking on operational AI, architecture, integration, and platform engineering for organizations with real complexity and regulatory weight.
Filtered by Web platform · clear
An agent filling a form today reads the rendered page and infers. WebMCP lets the page declare the same capability as a named tool with a schema. Two attributes on the form, one per field, and no script. The demonstration below runs in this article.
Read insightThere is a widely held expectation that web pages end up as a prompt box. WebMCP is the more modest version of that future: the application stays visible, and a prompt is added as a second way to operate it. Two things have to exist for that to work. Only one of them is yours to build, and whether you build the second one as well is the decision about who controls the agent.
Read insightA form completed through WebMCP should run the same authentication, authorization and business rules as one filled in by hand. The security question WebMCP actually raises is not whether the backend needs to change. It is whether the action a valid, authorized agent just took is the action the user meant.
Read insightNewsletter
A short email when we publish something worth your time. Architecture, integration, and operational AI in regulated organizations. No cadence promises, no forwarding your address.