https://vibecoding.rest/category/browser-automation/Recent content in Browser Automation on Vibe CodingHugoenhttps://vibecoding.rest/mcp-servers/puppeteer/Mon, 01 Jan 0001 00:00:00 +0000https://vibecoding.rest/mcp-servers/puppeteer/<p>The Puppeteer server gives an agent control of a real (or headless) Chrome browser — navigating to URLs, clicking elements, filling in forms, and capturing screenshots as it goes.</p> <h2 id="why-it-matters">Why it matters</h2> <p>Some tasks can only be verified by actually looking at rendered output — a UI change, a broken layout, a JavaScript-heavy page that a plain HTTP fetch can&rsquo;t render. Browser automation closes that verification gap.</p>https://vibecoding.rest/mcp-servers/playwright/Mon, 01 Jan 0001 00:00:00 +0000https://vibecoding.rest/mcp-servers/playwright/<p>Playwright MCP gives an agent structured control over a real browser — Chromium, Firefox, or WebKit — using Playwright&rsquo;s accessibility tree instead of pixel-based screenshots. It exposes tools for navigation, clicking, form filling, and page inspection so an agent can complete multi-step web tasks deterministically.</p>https://vibecoding.rest/mcp-servers/chrome-devtools/Mon, 01 Jan 0001 00:00:00 +0000https://vibecoding.rest/mcp-servers/chrome-devtools/<p>Chrome DevTools MCP connects a coding agent to a live Chrome instance, exposing the same network, console, and performance-tracing tools available in DevTools. It lets an agent navigate pages, inspect requests, read console errors, and record performance traces from inside its own workflow.</p>