Vercel has added experimental WebMCP support to mcp-handler. Here is what it means for UAE websites and ecommerce teams, and where a sensible owner should draw the line.
Vercel has added experimental WebMCP support to mcp-handler, a package for exposing Model Context Protocol tools. The update lets a website make selected tools available to in-browser AI agents through a single script tag, rather than requiring a separate browser-side OAuth flow. The announcement was published on 18 September 2026. (vercel.com)
The important detail is that this is an opt-in feature. A developer chooses which tools to expose through the `experimental_webMcp` object. Vercel’s example registers a tool called `roll_dice`, then loads `/api/mcp?webmcp-script` on the page. That script registers the selected tools with the page and sends calls back to the MCP server as the signed-in user. (vercel.com)
This is not a new chatbot for your website. It is a way for a browser agent to use selected functions that your website already provides.
Traditional browser automation usually asks an agent to inspect a page, identify buttons or fields, and simulate clicks and typing. WebMCP gives the page a clearer interface for agent actions. The proposed standard allows developers to expose JavaScript functions or HTML forms as tools with descriptions and structured input schemas. (github.com)
The browser agent discovers the tools available on the current page. It then sends structured arguments, the page executes the relevant client-side logic, and the result comes back to the agent. The visible interface can remain in sync because the site’s own code performs the action. (github.com)
For a UAE retailer, one carefully designed tool might be `find-products`. It could accept a category, size, colour and stock preference, then update the product grid. Another might prepare a basket for the customer to review. The agent would not need to guess which filter to open or which button means “add to basket”. These are practical applications of the WebMCP model, not features Vercel has announced for a particular UAE store.
The opportunity is mainly for businesses with a useful, interactive website. A catalogue, booking site, ecommerce shop or customer portal could expose a small set of actions that agents can complete while the customer remains on the site.
That could make an Arabic-English product search, a delivery-area check or a quotation request easier for an agent to handle. It could also help a customer move from “find something suitable” to “show me the options and prepare the next step” without relying on brittle screen scraping. The WebMCP proposal describes this as a cooperative workflow where the user, page and agent share context, rather than a fully autonomous replacement for the website. (github.com)
The limitation matters. WebMCP is still a proposed web standard, and Vercel describes this mcp-handler support as experimental. It is intended to complement backend integrations, not replace them, and it is designed for browser-mediated workflows where a page is present. (vercel.com)
A business should also treat every exposed tool as an action surface. A tool that only searches products has a different risk from one that changes an order, reveals account information or starts a payment. Descriptions, input validation, user confirmation and server-side permissions still matter. Passing the signed-in user’s session through the browser is convenient, but it does not make poor access controls safe.
Start with a capability audit, not a framework upgrade. List the actions customers already take on the site and separate low-risk discovery from high-impact account actions.
For a new site, ask the developer to structure important actions as clear functions with defined inputs and outputs. For an existing site, do not rebuild a stable website simply because WebMCP is available. The sensible first step may be to document the current flows and identify one useful, low-risk experiment.
If the project needs a broader rebuild, Paknology’s websites and mobile apps service is the relevant starting point. If agent actions must connect to stock, accounts or operations, the ERP and automation service is the more relevant conversation.
The technical detail is set out in Vercel’s WebMCP changelog entry, which points developers to the mcp-handler documentation. The underlying WebMCP proposal also explains the browser tool lifecycle and its security model. (vercel.com)
Paknology has a commercial interest when a UAE business needs a new website, mobile app, or an automation project that connects the site to internal operations. That does not mean WebMCP belongs on every project. A simple brochure site, a low-traffic landing page or a stable shop with no clear agent use case may be better served by leaving the site alone and improving its normal user experience.
A sensible next step is to bring one customer journey, one set of permissions and one low-risk tool definition to a web review. If the site needs a wider build or integration, start with websites and mobile apps; if it does not, document the idea and wait for a clearer business case.
Sources
Book a free consultation and get a clear roadmap — from company formation to a fully automated digital operation.