
Teikametrics MCP Explained: Connecting Amazon, Walmart & TikTok Data to Claude
What if your e-commerce data could talk directly to Claude? In this episode, Teikametrics CEO & Founder Alasdair McLean-Foreman breaks down the launch of the Teikametrics MCP — and why the team deliberately built it around proprietary optimization, content, and catalog data rather than simply mirroring what already lives in Amazon, Walmart, or TikTok. Alasdair explains where LLMs genuinely add value (stitching together siloed data from inventory, finance, and content systems) and where they don't (directly optimizing your ad levers — that's what a vertical AI orchestration layer is for).
The beta launches at the end of July — listen in to learn how early users are already putting it to work, and how to become one of them.
Key Takeaways
Proprietary data is the point. Amazon's MCP already exposes Amazon's data. Teikametrics built its MCP around what only lives in its platform — optimization data, content recommendations, and catalog outputs — so customers unlock signals they can't get anywhere else.
LLMs are for stitching, not steering. Alasdair is clear that customers shouldn't use Claude to directly optimize Amazon, Walmart, or TikTok ads — that requires a vertical AI orchestration layer, which is what the Teikametrics platform does. The MCP shines when combining Teikametrics data with inventory, finance, or content systems.
The Ask Elephant example set the template. Teikametrics saw the power of MCP internally by piping sales-call transcriptions from Ask Elephant into Claude and stitching them with product data — and set out to replicate that experience for customers.
Catalog review at scale is a killer use case. With Amazon's July 27 content title change requirement, brands can pull Teikametrics' AI catalog recommendations into Claude and check them against their own brand voice and IP guidelines — practical when reviewing 10,000 SKUs in a UI isn't.
Customers will find the use cases. The beta is a deliberate "wide door": Teikametrics expects design partners to discover applications the team hasn't imagined, and those discoveries will feed back into the core product roadmap.
"We have AI" is a dead marketing message. At Cannes, generic AI banners have given way to companies showing howAI is actually being used — and MCP is a concrete example of functionality over hype.
Read first, write carefully. V1 of the MCP surfaces data out of the platform. Read-write capabilities — letting Claude make changes inside Teikametrics — are on the roadmap, but will be rolled out cautiously with design partner feedback.
0:00 — Introduction: Exposing proprietary data, not marketplace data
0:49 — Dispatch from Cannes: Amazon's takeover, Walmart's CTV push, TikTok's creator economy
3:03 — Why "we have AI" doesn't land anymore
3:55 — Introducing the Teikametrics MCP
4:51 — The Ask Elephant + Claude example that inspired the strategy
6:15 — Use case: reviewing 10,000 SKUs of catalog content in Claude
7:49 — What the MCP does (and doesn't) do in v1
9:20 — Why not just use Amazon's MCP? The orchestration layer argument
11:33 — Beta launch, design partners, and what success looks like
13:09 — Breaking down data silos: inventory, finance, and reporting
14:40 — Timeline: end-of-July release and the read-write roadmap
Flere episoder fra "Human in the Loop"



Gå ikke glip af nogen episoder af “Human in the Loop” - abonnér på podcasten med gratisapp GetPodcast.








