Chrome DevTools MCP alternative
Browser commands shaped for coding agents
DevSnoop is a Chrome DevTools MCP alternative for coding agents that need a smaller browser command surface. It focuses on the frontend loop agents repeat most: summarize the page, find the control, click it, read failures, and confirm what changed.
Choose DevSnoop when you want compact browser automation commands over a local HTTP API instead of asking the agent to reason through broad DevTools context.
Chrome DevTools MCP support notes
Chrome DevTools MCP is still useful when the agent needs broad protocol access. DevSnoop fits the narrower support loop: local tab, actionable selector, command result, diff, logs, and screenshot only when needed.
Setup path
Chrome DevTools MCP usually means adding MCP config to the agent. DevSnoop exposes localhost:9400 through the native host, so any agent that can run curl can use it.
Context shape
DevSnoop returns condensed page summaries, element records, selectors, and tab IDs instead of asking the agent to interpret raw browser internals for every check.
Support workflow
When an agent gets stuck, use `get_logs`, `get_network`, `inspect_element`, and `diff` to narrow the failure while keeping the same local browser tab alive.
Command mapping
| Task | DevSnoop | Chrome DevTools MCP |
|---|---|---|
| Summarize current page | page_summary | Snapshot or DOM inspection |
| Find a control | find + inspect_element | DOM query and manual interpretation |
| Verify after click | click + diff | Click action plus fresh snapshot |
| Debug failure | get_logs + get_network | Console and Network panels |
| Visual confirmation | screenshot | Screenshot tool |
The usual browser-agent path
- Raw DevTools context can be broad, noisy, and expensive for simple UI verification loops.
- Agents still have to translate page structure into selectors and repeat context gathering after every interaction.
- Screenshot-first checks are easy to start but burn tokens when the agent only needs a compact page or diff summary.
What DevSnoop changes
- Starts with `page_summary`, `find`, and `inspect_element` so the agent gets selectors and structure immediately.
- Uses `diff` after clicks, fills, and navigation to confirm changes without re-reading the whole page.
- Keeps logs, network failures, screenshots, storage, and tab control behind one local HTTP API.
Best fit
- Agent-driven UI checks where selectors, diffs, and logs matter more than raw protocol access.
- Developers who want Chrome automation without wiring an MCP server into every agent.
- Local frontend debugging with screenshots available only when visual confirmation matters.
Use DevSnoop when you want a smaller browser command surface tuned for agent-driven frontend development.
$29
one-time license
24h
full-command preview
Local
Chrome extension and host