# Do I need to install WebMCP on my Shopify storefront?

> Liquid and the Hydrogen preview include standard tools. Custom work needs a named operation, browser support, test, and owner.

August 22, 2026 · Updated September 21, 2026 · Sources checked September 21, 2026

https://app.ai-commerce-ready.com/blog/shopify-webmcp-liquid-storefronts-2026/

## When this applies

A vendor offers WebMCP installation, or a custom storefront project says it depends on browser agent tools. [1]

## When this does not apply

A standard Liquid storefront or the Hydrogen developer preview already supplies the tools. Without a named custom dependency, there is no installation project to approve. [1]

## Why this matters

Paying to recreate built-in tools adds work without establishing whether a custom agent needs it. [1]

## What to do

Decline duplicate built-in setup. For custom work, require the stack, operation, supported browser, acceptance test, and maintenance owner. [1]

## When you’re done

You have declined unnecessary installation, or have a written scope and a named owner for testing one custom dependency. [1]

## What this cannot prove

A callable tool does not prove traffic, product selection, or sales. Hydrogen remains a developer preview. [1]

## Paid help and free options

- When paid help makes sense: Consider paid development only for a named custom dependency with a testable result and a maintenance owner. The storefront stack alone does not justify the purchase. [1]
- What’s already free: Shopify supplies standard WebMCP tools on Liquid storefronts and the Hydrogen developer preview without merchant installation or configuration. [1]

**Liquid storefronts do not need a WebMCP installation service.** Shopify's [WebMCP documentation](https://shopify.dev/docs/api/web-mcp) says standard tools are built into Liquid and the Hydrogen developer preview, without merchant setup.

WebMCP lets a compatible browser assistant call storefront tools. Shopify currently limits agent support to Chromium-based browsers; Hydrogen remains a preview.

## Ask what custom work adds

Before approving development, get:

1. The storefront stack and required operation.
2. The browser and tool support it depends on.
3. A test showing the intended shopper result, and a maintenance owner.

For another headless stack, ask its owner to demonstrate compatibility. The built-in support statement does not cover every stack.

Finish by declining duplicate setup or approving one named custom dependency with a test and owner. A callable tool proves no traffic, product selection, or sales.

## Sources

1. [WebMCP tools](https://shopify.dev/docs/api/web-mcp)