Massin SystemsBuilding & appsClaude
🔎 Let Claude see your live site (DevTools MCP)
Normally you describe a website bug to AI like a patient describing a symptom: "it looks weird on mobile." With the Chrome DevTools MCP connection, Claude opens your live site in a real browser and sees for itself — layout, console errors, slow requests, all of it. Diagnosis stops being a guessing game.
What it unlocks
- Sees the rendered page — not your description of it, the actual pixels and layout.
- Reads console errors — the error messages your visitors never report but always experience.
- Watches the network — which images and scripts are slow, missing, or huge.
- Interacts — clicks your nav, submits your form, reproduces the bug while you watch.
Setup (15 minutes)
- You need Claude Code (or another MCP-capable client) and Chrome installed.
- Add the Chrome DevTools MCP server — it's an official open-source project; the README gives the one config line. Restart your client.
- Test: "Open [your site] in the browser and describe what you see above the fold."
The prompts that earn their keep
Open [my site URL]. Do a full health check: console errors, failed or slow network requests, layout problems at mobile width (375px), and anything visually broken as you scroll the full page. List issues by severity, and for each: the likely cause and the fix.
Reproduce this bug: [what users report, e.g., "the contact form does nothing on phones"]. Interact with the page like that user, watch the console while you do it, and tell me exactly what fails and why.
My site feels slow. Load it, analyze the network waterfall, and give me the top 3 things making it slow, ranked by impact — with what each fix involves in plain English.
The fix-verify loop (the real magic)
Because Claude can both edit your code AND check the live result, you get a closed loop: find the bug → fix it → reload → confirm it's gone → check nothing else broke. What used to be an afternoon of you-describing and it-guessing becomes minutes.
Point it at your own sites. Browsing tools follow the same rules you should: analyze sites you own or have permission to test. And keep the checkpoint habits — commit before the fixing session starts.
Monthly health-check ritual: run the full-check prompt on your site the first Monday of each month. Sites rot quietly — links die, scripts update, images bloat. Ten minutes a month catches it early.
Want this done for you?
We set up these exact systems for businesses like yours. One call, honest scope, no pressure.