Tools & integrations, read from an operations desk

Latest

Commerce.com turns on WebMCP for nearly 100,000 storefronts

Commerce.com has enabled WebMCP across almost 100,000 domains using Cloudflare's edge. AI agents in a shopper's browser can call tools such as search_products and add_to_cart instead of clicking through pages. Merchants can opt out from their dashboard. WebMCP itself is still an experimental browser standard in early preview.

What changes for operators — If you sell through a Commerce.com store, agent access is now on by default, so check the opt-out switch in your dashboard and decide deliberately. If you run your own site on Cloudflare, the same edge WebMCP feature has been in beta since August, so you can test it without touching your theme. Treat it as a pilot: WebMCP sits behind experimental Chrome flags and in a few agentic browsers, so little real traffic will use it yet. The useful question for sales and ops is whether your catalogue, pricing and cart logic are clean enough for an agent to call, because the checkout step stays with the human buyer.

Cloudflare Opens Its Telemetry to AI Agents, Resets Pricing

For a 10-200 person company running Workers, R2, or AI Gateway on Cloudflare, this removes a chunk of integration work needed to make an AI ops or support agent actually useful during an incident: instead of building separate connectors for logs, traces, and analytics, an agent can hit one SQL API or the new Observability MCP server, and alerts can route straight to that agent via webhook before a human even opens a dashboard. Logpush moving off Enterprise-only plans also means smaller teams can now export raw logs to their own tools for agent training or audit trails without an enterprise contract, though the new per-GB pricing landing in December 2026 is worth checking against current log volume.

Cloudflare Adds Web Search to AI Gateway for Grounding Agent Responses

For a 10-200 person B2B company running support or sales agents, this removes a common failure mode: agents that hallucinate or 404 when guessing URLs to fetch current pricing, policy updates, or competitor info. If you're already using Cloudflare Workers or AI Gateway for inference routing and logging, adding grounded web search is now a one-line binding rather than a separate integration with a third-party search vendor, and it draws from the same billing and observability you already have.

Cloudflare's AI-agent browser adds WebMCP support

For a 10-200 person B2B company building or buying agents that need to pull data from websites, fill forms, or monitor competitor pages, this matters because WebMCP lets an agent call a site's exposed function (like searchFlights()) instead of guessing at pixels and DOM elements, cutting failure rates on brittle scraping workflows. Kitesurf also now works with standard tooling (Playwright, Puppeteer, MCP), so an ops or engineering team already using those frameworks for internal automation can swap in Kitesurf as the browser backend without rewriting scripts, and it's free during Cloudflare's beta behind per-account limits — worth testing before committing to a paid headless-browser vendor for agent workflows.

Cloudflare Lets Sites Block AI Training Without Losing AI Search Visibility

For a 10-200 person B2B company, this is a direct lever on lead generation through AI search. Buyers increasingly research vendors through ChatGPT, Perplexity, and AI Overviews rather than clicking blue links, so being retrievable and citable in those answers matters for pipeline. Until now, blocking AI crawlers to protect proprietary content (pricing pages, case studies, technical docs) also risked disappearing from AI-generated answers entirely. With this signal, an operator can tell crawlers: index and cite our content, but don't train on it. Marketing and RevOps teams should update robots.txt to declare this policy explicitly rather than relying on default crawler behavior, and should audit which AI bots (from OpenAI, Anthropic, Google, Perplexity) actually respect it, since compliance is voluntary.

Cloudflare Makes Python First-Class for AI Agents at the Edge

Most 10-200 person B2B companies won't touch this directly, but the teams and agencies that build their custom AI support bots, internal RAG search, or MCP-based assistants will feel it: Hyperdrive now lets a Python Worker query the company's existing PostgreSQL or MySQL database directly, and native langchain/openai support means an automation vendor can stand up a customer-facing AI agent or an internal knowledge assistant without maintaining a separate server or writing JavaScript adapters. For an operator evaluating build vs. buy on an AI support or ops tool, this lowers the engineering cost of a custom build running on Cloudflare's network, which is worth flagging to whichever contractor or in-house developer maintains your automation stack.

Cloudflare Opens Faster Verification Path for AI Bots and Agents

If your company's website sits behind Cloudflare, this directly affects how visible you are to AI search assistants like ChatGPT or Perplexity when prospects ask them for vendor recommendations. A verified bot listing means you can confidently allow specific AI crawlers through your firewall rules instead of blocking all bot traffic out of caution, which previously risked cutting your product pages, docs and pricing off from AI-generated answers. It also means unverified agents scraping your site under a fake identity are easier to identify and block, reducing wasted server load and the risk of automated abuse against contact forms or support chat.

Cloudflare Lets Sites Set AI Crawler Rules Once, Sync Everywhere

Most 10-200 person B2B companies run several web properties — marketing site, docs, blog, help center — often on different platforms, each needing separate bot rules to control AI crawler access. Bot Preference Sync means ops or marketing can set an AI access policy once (e.g., allow ChatGPT and Perplexity to cite content, block bots scraping for training) and have it apply consistently, without IT touching robots.txt on every subdomain. That matters directly for AI search visibility: getting cited correctly in AI Overviews or chatbot answers depends on crawlers being able to read the right pages while sensitive areas stay blocked. The catch is that sync only works where the receiving platform participates in Cloudflare's system, so it doesn't yet replace per-site vigilance everywhere content lives.