Scout
Drive real browsers from your agent with 84 CDP-based tools for scraping, UI checks, and vision-assisted automation.
Overview
Scout is an MCP server for the Build phase that provides 84 CDP browser automation tools with DOM diffing and vision hybrid control.
What is this MCP server?
- 84 browser automation MCP tools in Scout v1.11.1
- Pure Chrome DevTools Protocol (CDP) control without fragile-only selectors
- DOM diffing for efficient page change detection
- Vision hybrid mode combining screenshots with structural DOM signals
- OCI package ghcr.io/klarlabs-studio/scout:1.11.1 via stdio `mcp serve`
- 84 browser automation tools advertised
- Server version 1.11.1
- OCI image ghcr.io/klarlabs-studio/scout:1.11.1 with stdio transport
Community signal: 3 GitHub stars.
What problem does it solve?
Agents struggle to operate modern SPAs and auth-gated sites with only HTTP fetch or a handful of brittle browser shortcuts.
Who is it for?
Indie developers automating multi-step web flows, agent-driven QA, and research crawls that need CDP-depth instead of static HTML.
Skip if: Simple one-url HTTP pulls, teams blocked from running local Chrome/CDP, or compliance-sensitive scraping without human oversight.
What do I get? / Deliverables
After deploying the Scout OCI image over stdio, your agent can run full browser sessions with diff-aware and vision-backed tooling.
- Access to 84 Scout browser tools over MCP stdio
- CDP sessions with DOM diffing and vision-hybrid observation for agent tasks
Recommended MCP Servers
Journey fit
Browser automation MCP is shelved under build integrations because agents most often install it to implement flows against live sites. Integrations captures stdio OCI Scout as agent tooling; the same server supports ship-phase testing and idea-phase competitor browsing.
How it compares
High-tool-count browser MCP (84 tools), not a lightweight read-only web skill.
Common Questions / FAQ
Who is Scout MCP for?
Solo builders and agent users who need Chrome CDP automation, DOM diffs, and optional vision for complex web UIs.
When should I use Scout MCP?
Use it when building or testing flows that require clicks, navigation, visual verification, or competitor site automation beyond curl.
How do I add Scout MCP to my agent?
Pull ghcr.io/klarlabs-studio/scout:1.11.1, run stdio with arguments `mcp` and `serve`, and register Scout in your MCP server list.