WebMCP: Give an API to Web Apps That Don’t Have One
summary
Introduces WebMCP, applying the Model Context Protocol to browsers so web apps without APIs can expose structured functions via navigator.modelContext. Explains why DOM-scraping and vision-based agents fail, describes MCP concepts (Tools, Resources, semantic layer), shows an Agent Adapter extension technique to inject WebMCP into third-party sites, and demonstrates a live x10 speedup by replacing pixel/DOM scanning with native tool-calling for automation.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:17Missing APIs in web apps
- 3:06Limitations of automation
- 4:31DOM wall and MCP DevTools
- 7:10How MCP DevTools works
- 10:01What is WebMCP?
- 12:18Creating WebMCP tools
- 17:20WebMCP in action
- 20:03Live demo
- 25:03Why WebMCP over MCP server?
- 27:16WebMCP state and adoption
- 28:43Performance comparison
- 30:56Live performance test
- 37:00Injecting into legacy apps
- 40:49Multi-WebMCP demo
- 42:56Future and takeaways
- 45:51Q&A
