
Scout
io.github.klarlabs-studioPublished by GitHub account klarlabs-studiov1.15.3Updated Oct 24, 2026
Browser automation MCP server with 84 tools. Pure CDP, DOM diffing, vision hybrid.
Overview
Scout is a single-binary browser automation MCP server that gives an AI assistant a real Chrome browser to navigate, click, fill forms, extract content and…
- What you can do
- Navigate pages and take structured observations, including DOM diffs and token-budgeted snapshots
- Click, type, hover, drag, select options and fill forms semantically
- Extract text, tables, markdown, readable content and accessibility trees
- Capture screenshots, annotated screenshots, PDFs and screen-recording video
- Inspect network requests, console errors, cookies, tabs, iframes and detected frameworks
- Record and replay deterministic action playbooks, run batches and traces
- When to use it
- Useful when an assistant needs to operate real websites rather than just read them: filling in forms, checking a page after a change, scraping structured content, or driving a local dev server. It suits users who want browser control without installing Node.js or Playwright.
- Requirements
- Runs as a local process started with the scout mcp serve command; the manifest ships it as a container image, and the README also lists Homebrew, a direct binary and Go install. A Chrome browser must be available for it to launch. No API keys are declared for the MCP server itself; the optional chat UI needs a provider key such as ANTHROPIC_API_KEY or OPENAI_API_KEY.
Installation
In SourceWeft
- Open Scout in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Scout
Browser automation, one binary. The simpler alternative to Playwright — no Node, no Python, no runtime. Drive a real browser from Go, any shell, any AI agent (built-in MCP server), or a chat UI.
[Release] [License] [CI] [Go Reference] [Coverage] [Security (nox)]
A single statically-linked scout binary gives you a CLI, an 87-tool MCP server (so any MCP-aware agent — Claude Desktop, Cursor, Cline, custom — has a browser), a conversational chat UI, and a Go library with Gin-like middleware composition. Same engine, four access points.
vs. Playwright
Quick Start
Install
MCP Server — 77 Tools
Run scout mcp serve and any MCP-aware agent has a browser. No second project to install, no Node runtime, no Python interpreter — the binary is the server. Configure in any MCP client:
Tool Categories
All tools have MCP annotations (ReadOnly, OpenWorld, ClosedWorld, Idempotent) for smart auto-approval. Read-only tools like observe, extract, and screenshot run without permission prompts.
Runtime Configuration
Switch between headless and visible browser without restarting, and opt into local-dev workflows (loopback, private IPs):
The MCP server also reads SCOUT_ALLOW_PRIVATE_IPS=1 at startup as a one-shot toggle for trusted environments.
Screen Recording (video)
Record the active page as a video. Pure CDP — works in headless, no Playwright needed. Recording survives navigate, open_tab, and switch_tab calls in between, so a multi-page demo lands as one continuous clip:
If ffmpeg is on PATH, the result is encoded to WebM (libvpx-vp9) or MP4 (libx264). If not, scout returns the raw JPEG frames directory plus an ffmpeg concat list so you can encode offline. The result is always a file path, never base64 — never enters your LLM token budget.
Realistic FPS: ~10–15 on typical pages, capped at 30. Implementation polls Page.captureScreenshot (CDP Page.startScreencast events are silently dropped under --headless=new Chrome).
Browser UI
A conversational browser automation interface. Type natural language, watch the browser respond in real-time.
The UI streams AG-UI protocol events over SSE:
- Chat panel with markdown rendering and quick-action pills
- Live browser viewport with screenshot streaming and URL bar
- Activity timeline showing tool calls in real-time
- Stop button to cancel mid-stream
The Go server handles the agentic loop: LLM decides which scout tools to call, executes them, streams browser state deltas back to the frontend. Supports any OpenAI-compatible endpoint via --base-url.
Agent Package (Go)
High-level Go API for callers that want to embed scout in a program. Structured output, auto-wait, goroutine-safe. Most users reach scout through the CLI or MCP server above — this section is for the Go-library path.
Core Library (Go)
Gin-like Engine/Context/Group/HandlerFunc with middleware composition. The lowest-level Go API — use it when you want full control of task lifecycle, named groups, and middleware chains:
Middleware
CLI
The CLI is a deliberate one-shot tier: each command launches a browser,
navigates, runs one read/diagnostic action, prints the result, and exits.
Stateful interactive flows (click→type→submit, multi-tab, live cookie/network
manipulation) live in the MCP server (scout mcp serve) and chat UI
(scout ui serve), which keep a session alive across actions.
CLI defaults to visible browser (--headless to hide):
Architecture
Security
Vulnerability scanning runs on every push and PR via nox. Findings are uploaded to GitHub code scanning, annotated inline on PRs, and gated against .nox/baseline.json so regressions block merges. The status badge in the header reflects the latest main-branch scan.
nox also drives dependency remediation in place of Dependabot — the Nox Remediate workflow runs weekly (Monday 06:00 UTC) and on demand, executing nox fix against fresh OSV.dev findings and opening a single PR with the verified upgrades.
License
MIT
Source: README.md at commit f45eb04
Tools
0Version history
1- v1.15.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts