> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/connectors/webmcp.md). # WebMCP Tools published by the page the assistant is embedded on. Marked `BROWSER` in the connectors list, and enabled by default. WebMCP lets **the page itself** publish tools to the assistant, using the WebMCP standard. {% hint style="info" %} WebMCP is a web standard, not a Maker one. For code examples of tools you can publish, see [WebMCP](/maker-greatstore/developer-reference/webmcp.md). Chrome's [WebMCP overview](https://developer.chrome.com/docs/ai/webmcp) and [imperative API](https://developer.chrome.com/docs/ai/webmcp/imperative-api) documentation are the reference for the standard itself. {% endhint %} Where other connectors are servers the assistant calls, WebMCP tools live in the browser, on the page the shopper is currently looking at, which means the assistant can act on the page, not just talk about it. ## The canonical example: add to cart A storefront can define an **add-to-cart tool** via WebMCP. A shopper viewing a product can tell the assistant "add this to my cart", and the assistant calls the page's tool and the item is actually added, on the page, with no custom integration work. ## What else it can do Add-to-cart is just the most obvious one. Because the tools run on the page the shopper is already on, WebMCP fits anything the shopper would otherwise do by clicking around themselves. A few examples: * **Change a product's options**: the shopper says "show me this in medium, blue" and the assistant switches the variant on the page, updating the image and price. * **Update the cart**: change a quantity, remove an item, or apply a promo code without the shopper leaving the conversation. * **Move through checkout**: start checkout, or jump to the shipping or payment step, when the page exposes those as tools. * **Filter and sort a listing**: on a category or search page, narrow results ("only show items under $50, in stock") by driving the page's own filters. * **Fill and submit a form**: book an appointment, start a return, or sign up for restock alerts using the fields already on the page. * **Navigate the site**: open the size guide, jump to reviews, or go to the shopper's orders, so the answer and the destination arrive together. What's on offer is entirely up to the page: WebMCP lets a site expose *any* on-page action as a tool, and the assistant can use whichever ones it publishes. [WebMCP](/maker-greatstore/developer-reference/webmcp.md) has working code for each of these. ## Relationship to page context WebMCP is the *active* counterpart to [JavaScript API](/maker-greatstore/developer-reference/javascript-api.md): context tells the assistant what is on the page, WebMCP lets it do something about it. {% hint style="info" %} Like every connector, WebMCP sits in the priority order: a page-published tool can override a server-side one of the same name. {% endhint %} ## Access control WebMCP tools are defined by the page at runtime, so there is no fixed list to configure in advance. You get the three group settings (**Write tools**, **Read-only tools**, **Other tools**), and a page-defined tool is offered to the assistant only if its group is set to Allow. Disallowing **Write tools** here is the switch that stops the assistant acting on the page, add-to-cart included, while leaving it free to read page context. See [Controlling tool access](/maker-greatstore/connectors/tool-access.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.maker.co/maker-greatstore/connectors/webmcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.