{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/65a025e83efd45c795eac940a014e3bd\" frameborder=\"0\" width=\"2218\" height=\"1663\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1663,"width":2218,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1663,"thumbnail_width":2218,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/65a025e83efd45c795eac940a014e3bd-0bf41a26ce4042fe.gif","duration":58.46,"title":"Building an MCP with Opus and Playwright","description":"This Loom explains how Automatt leveraged Opus 4.8 to build an MCP for its core studio product. It describes turning one-off browser automations into deterministic code blocks that run in the best environment for authoring, using computer-use agents. Gotham asks Claude to generate a quick demo where it selects a random Wikipedia article about philosophy and walks through it. The demo reportedly builds the automation as Playwright code and then runs it through the Automatt studio reliably, showing the automation executing on the Wikipedia philosophy pages."}