Hydrogen 2026.1.4 MCP Proxy: Expose Your Catalog to AI

What 2026.1.4 Actually Shipped

• Automatic /api/mcp proxy. Incoming requests to /api/mcpare forwarded to Shopify's Storefront MCP server without a custom route handler.
• Default-on behaviour. Controlled by proxyStandardRoutes in createRequestHandler. That flag defaults to true.
• Multi-surface MCP support. Catalog MCP, Storefront MCP, and Checkout MCP all reachable through the same proxy.
• No auth required for public queries. Public catalog discovery works without credentials. Authenticated operations use the existing Shopify-Storefront-Private-Token.
• Built for agentic commerce. Shopify explicitly targets ChatGPT, Claude, Perplexity, and the broader MCP-agent ecosystem.

How the /api/mcp Proxy Works

Three-stage request flow:

1. An MCP client (ChatGPT, Claude Desktop, a custom agent) sends a request to https://your-store.com/api/mcp.
2. Hydrogen's Oxygen runtime intercepts the route, checks proxyStandardRoutes, and forwards the request to Shopify's Storefront MCP server scoped to the merchant.
3. The MCP server responds with product data, policies, or carts; Hydrogen streams the response back to the client.

Three MCP Surfaces Shopify Exposes

Enabling the Proxy in Your Storefront

The flag is on by default. You only touch this if you want to disable or customize it.

// server.ts
import { createRequestHandler } from "@shopify/hydrogen";

export default {
  async fetch(request: Request, env: Env, executionContext: ExecutionContext) {
    const handleRequest = createRequestHandler({
      build: remixBuild,
      mode: process.env.NODE_ENV,
      getLoadContext: () => ({ /* ... */ }),

      // ── Storefront MCP proxy ──────────────────────────────────────
      // true (default): /api/mcp is forwarded to Shopify's MCP server.
      // false: you own /api/mcp; AI agents won't auto-discover you.
      proxyStandardRoutes: true,
      // ─────────────────────────────────────────────────────────────
    });

    return handleRequest(request);
  },
} satisfies ExportedHandler<Env>;

Upgrade path: bump @shopify/hydrogen to 2026.1.4 or later, redeploy, and the proxy is live. No additional configuration.

How ChatGPT / Claude / Perplexity Wire In

Each agent treats your /api/mcp endpoint as an MCP server. Configuration differs by client.

Authentication and Private Tokens

Two tiers of access:

• Public queries — product listings, prices, availability, policies. No auth required. This is how discovery and recommendation agents see you.
• Authenticated operations — cart mutation, customer-specific pricing, account-bound actions. Require the Shopify-Storefront-Private-Token header, which Hydrogen already injects on its Storefront API calls.

Preparing Your Catalog for AI Shoppers

The proxy is free. The competitive advantage is catalog hygiene. Five things to do before AI shoppers arrive:

• Structured product attributes. Size, colour, material, capability as explicit metafields. Free-text descriptions are hard for agents to filter; structured attributes are native.
• Accurate availability. Inventory out-of-stock flags must match reality. Agents that recommend a bought-out product produce buyer friction that maps back to your brand.
• Authoritative policies. Return, shipping, and warranty policies published as structured content so the agent can quote them back to shoppers without hallucination.
• FAQ coverage. Ship an FAQ block that covers the top-20 buyer questions. Storefront MCP surfaces FAQs directly — buyers get answered by your content, not a made-up response.
• Product photography that matches the data. Agents mostly work in text for now, but multimodal agents are landing in 2026. Consistent photography will matter as they arrive.

Agentic Checkout Via Checkout MCP

The commerce value unlock. An AI agent can build a cart, populate shipping / billing from the buyer's profile, and submit a checkout — all without leaving the chat interface. Payment authorization still happens with the buyer (card confirmation, Apple Pay / Google Pay biometrics, 3DS step-up when applicable).

Monitoring MCP Traffic

Instrument MCP as a separate traffic source the same way you instrumented organic search a decade ago. Break out by user-agent (expect chatgpt-agent, claude-bot, perplexity-shop, and custom agent strings), by tool call (search vs. cart vs. checkout), and by conversion rate.

Agency Rollout Playbook

1. Upgrade sandbox storefronts to Hydrogen 2026.1.4 this week. Verify /api/mcp returns a valid MCP response.
2. Audit client catalogs against the five catalog-readiness items. Most agencies find at least two fail on every client.
3. Ship MCP analytics tiles (requests, sessions, conversion) to every client dashboard. This is the metric clients will ask about by Q3 2026.
4. Pilot agentic checkout with one enthusiastic client. Track the cohort separately for 60 days to establish benchmarks.
5. Publish your MCP endpoint in structured product schema on every PDP so discovery agents confirm canonicality.

Conclusion

Hydrogen 2026.1.4 made AI-agent-ready commerce a default. The engineering effort is a version bump. The real work — and the real differentiation — is in catalog hygiene, policy authority, and analytics discipline. Agencies that have a playbook for those three now will see MCP-sourced revenue appear ahead of agencies who wait.

Frequently Asked Questions