
How I Built a Claude Tool That Screenshots Every Page It Visits
How I Built a Claude Tool That Screenshots Every Page It Visits Claude is incredibly powerful. I use it in Claude Desktop to browse websites, fill forms, extract data, monitor pages. But Claude is text-only. When Claude clicks a button, it can't see the result. When Claude submits a form, it can't see the confirmation page. It's working blind. So I built an MCP tool that changes that. After every browser action, it screenshots the page and shows Claude what it's looking at. Now Claude can actually see . The Problem: Claude's Tool Calls Are Invisible Here's what using Claude with browser tools feels like: I ask Claude: "Check if that button is clickable" Claude calls my inspect_page tool Tool returns: { button_found: true, clickable: true } Claude continues But Claude has no idea what the button looks like Claude is working from text descriptions. If my tool makes a mistake, Claude doesn't know. If the page renders differently than I described, Claude goes off the rails. The Solution: V
Continue reading on Dev.to Webdev
Opens in a new tab



