The AI Native Dev - from Copilot today to AI Native Software Development tomorrow Why Every Developer needs to know about WebMCP Now
29 snips
Mar 31, 2026 Maximiliano Firtman, a 30-year web developer and author now focused on web-facing AI, talks about agents visiting websites and why screenshots are a dead end. He explains WebMCP, a Chrome API that lets sites expose callable client-side functions. They discuss e-commerce, payments, client-side models, and how in-browser AI and local models change web app design.
AI Snips
Chapters
Transcript
Episode notes
WebMCP Is A Client Side Tool Registry
- WebMCP is primarily client-side JavaScript: tools run in the browser and can call cloud/backends, hardware, or interrupt to ask the user.
- It's not automatic: developers must implement navigator.model registrations in their code.
Use WebMCP For Client State And Secure Hardware Flows
- Use WebMCP for client-held state or hardware flows (shopping carts, Apple Pay) where you don't want to expose server APIs externally.
- Prefer WebMCP when security or UX requires actions inside the browser context.
WebMCP Adds Agent Events And UI Hooks
- WebMCP includes events and UI hints so sites can detect and signal when an agent (tool) is controlling the page.
- Developers can change UI via CSS pseudo-classes and listen to toolactivated/toolcancel events to show agency state.