AI Weekly Malaysia

Shopify announced that browser-based AI agents can now complete purchases on eligible merchants' sites, extending its earlier WebMCP support from product search and add-to-cart into checkout, including Shop Pay. The update ships three new tools — get_checkout, update_checkout, and complete_checkout — letting an agent read the checkout screen, change details like address or delivery option, and submit the order once the buyer authorizes it, without screenshots or page scraping. Shopify already runs a hosted MCP server for server-to-server agents; both paths sit on its Universal Commerce Protocol (UCP), and the feature is rolling out to all eligible merchants according to Shopify's Gil Greenberg, who works on agentic commerce. The move runs opposite to Amazon and Adidas, which the article says are blocking AI agents from purchasing on users' behalf.

Why: If you run a Shopify storefront, agent traffic can now finish checkout instead of stalling at the cart — so you have to decide whether to leave it enabled or block agents the way Amazon does, and check whether your checkout customizations survive an agent editing address and delivery fields. If you build agents or commerce tooling, this is a concrete interface to target: implement get_checkout, update_checkout and complete_checkout (or the hosted MCP server path) rather than driving checkout with screenshots and scraping. For founders evaluating agentic commerce in Malaysia or SEA, the practical question is whether agent-completed orders change your payment, fraud or fulfilment assumptions before you enable it.

Cloudflare published a follow-up on Kitesurf, the browser it launched in August that runs entirely on Cloudflare Workers, and the headline change is WebMCP support: sites can expose callable tools (the post uses searchFlights() and Cloudflare Radar's navigate-to / set-location as examples) so agents call functions instead of simulating clicks. Kitesurf also added a batch of browser standards — CSS Layout, CSSOM, CSS Typed OM, custom elements, plus URL-based module resolution, JSON modules, and import map handling — aimed at rendering heavier JavaScript-chunked pages. You can try it in Cloudflare's public Kitesurf playground or point an agent at it via a chrome-devtools-mcp config using a wss:// browser-run devtools endpoint with browser=kitesurf and --category-experimental-webmcp.

Why: If you build or operate agents that touch websites, this gives you a concrete alternative to pixel-clicking: check the Application tab in DevTools on a target site to see whether it already publishes WebMCP tools, and if it does, wire your agent to call them. The MCP config in the post (chrome-devtools-mcp@latest pointed at the browser-run WebSocket endpoint with --category-experimental-webmcp) is copy-pasteable, so you can test tool-calling against Radar without running your own headless browser. Caveat: this is Cloudflare announcing its own product and the post claims Kitesurf is now 'more capable and more efficient' without publishing any benchmark numbers, so treat the efficiency claim as unverified.