The Death of the PDP: Why the Model Context Protocol (MCP) is the New Storefront

As a CTO, I've spent my career navigating technological shifts, but rarely have I seen one as profound as the current transformation in commerce. It's this very shift that inspired the founding of my new venture, Liminal Velocity.

"Liminal" refers to a threshold, a transitional phase, a period of in-between. We are precisely in such a phase in commerce—moving beyond the familiar but not yet fully understanding what comes next. The "Step" signifies our commitment to actively moving beyond this boundary phase, to build and define that murky future. As Alan Kay famously said: "The best way to predict the future is to invent it." At Liminal Velocity, we aren't waiting for the future of commerce to arrive; we are building the protocols to meet it.

Since the birth of eCommerce, we’ve been obsessed with the Product Detail Page (PDP). We’ve poured billions into conversion rate optimization (CRO), perfecting hero images, and shaving milliseconds off page loads.

I'm here to tell you: the PDP is becoming a legacy bottleneck.

We are shifting from a "Pull" economy (users searching for SKUs) to an "Outcome" economy (agents solving problems).

1. From SEO to Agentic Context (Enter MCP)

The "Spear-fisher" shopper is done with search bars. If my 3D printer breaks, I don't want to browse—I want to print again! The bridge to this future is the Model Context Protocol (MCP). Instead of a user landing on a PDP, their personal AI agent uses MCP to securely "interview" a brand’s knowledge graph. It’s no longer about whether your website is pretty; it's about whether your MCP server provides the high-fidelity, real-time context (inventory, compatibility, specific use-case telemetry) that an LLM needs to make a recommendation.

2. The Bifurcation of Commerce Architecture

The middle ground is dying. Commerce is splitting into two distinct technical stacks:

• The Utility Stack: Headless, API-first, and MCP-enabled. Here, the "shopper" is an AI agent acting on the user’s behalf. Your "conversion" depends on data structuredness and RAG (Retrieval-Augmented Generation) accuracy, not UI.

• The Experience Stack: Social, immersive, and serendipitous. This is where "browsing" lives—on TikTok or in VR—where the product is discovered through narrative and social proof.

3. The New CTO Mandate: Data Over Display

If the AI Agent is the primary "shopper," our engineering focus must pivot:

• From Pixels to Protocols: We need to stop building "pages" and start building robust, agent-ready interfaces. If your RAG inputs are stale or your inventory isn't current within the model's context, you are invisible.

• The Personal Data Vault: We must design for a world where users own their data. The AI agent knows the user's constraints; our systems must learn to provide solutions without needing to "capture" the user's identity first.

• Outcome-Based Telemetry: Success isn't "Add to Cart." It’s "Problem Solved." The conversation persists—the agent follows up to ensure the part worked and suggests the next logical upgrade based on actual performance.

The era of the PDP is over. We are no longer building destinations; we are building participants in a global, agentic conversation. Are you building for the click, or for the protocol?

[Note: MCP is in it’s infancy; I plan to follow up with a detailed post on MCP limitations and future opportuinities]

#CTO #AI #MCP #AgenticCommerce #FutureOfTech #EcommerceArchitecture #LiminalVelocity #Innovation