A developer configured a production WordPress multilingual plugin entirely through Claude Code using the Chrome DevTools MCP, without ever touching the browser manually. The Chrome DevTools MCP gives Claude access to the browser via the Chrome DevTools Protocol, allowing it to navigate pages, fill forms, upload files, run JavaScript, and read the accessibility tree. The session covered logging in, configuring language settings, placing widgets, uploading plugin zip files, and debugging issues like a cookie overriding language detection, a misconfigured Query Loop block wiping category filters, and broken Open Graph tags for social crawlers. The post also covers setup instructions, a Claude Code hook to auto-launch Chrome with remote debugging, and honest notes on rough edges like oversized screenshots and missed pop-ups.

11m read timeFrom blog.codeminer42.com
Post cover image
Table of contents
How Chrome DevTools MCP reads the pageConfiguring languages on productionUploading plugin updatesThe diagnosis I couldn't find myselfHow a hidden cookie silently overwrote the language detectionThe hidden settingTesting what Facebook actually sees vs. what the browser rendersWhat I actually typeWhat makes this different from browser automationSetting it upWhy I keep using it

Sort: