Charles JonesWebMCP lets a web page declare tools an AI assistant can call: list the services, check whether the 14th is free, make the booking.
Without it, an assistant visiting your site has to infer everything from the markup — reading a page built for human eyes and guessing which text is a price and which button submits a booking. With it, the page states plainly what can be done and how.
The shift underneath it
For thirty years the web’s contract has been: publish a document, let a browser paint it, let a person decide. WebMCP adds a second contract alongside it: publish a set of actions, let a program call them, let a person approve the result.
Both run on the same page. Nothing is replaced.
Why the standard route matters
Any site could already expose an API and document it. Almost none do, and no assistant would know where to look. A standard means the assistant does not have to know anything about your site in advance — it asks the page what it can do, and the page answers.
That is the entire value: discovery without prior arrangement.
What it does not do
WebMCP does not make an assistant trust you, rank you, or recommend you. It makes you legible. A business that is legible and wrong will simply be wrong faster.