Browser connectorMixed MCP + CDP

Hosted browser automation for MCP clients

Scout's browser connector is the broadest public surface: a hosted MCP server for clean browser sessions, CDP-backed automation, and multi-step web workflows.

navigateinspectextractreplay

See connector reference Browse connectors

The instrumented window

Glass, network light, accessibility trees, and a visible browser frame that feels ready to be driven rather than merely observed.

A stack of clean browser chambers: isolated enough for repeatable automation, alive enough for real page behavior, and transparent enough for an agent to reason through every step.

Identity

Browser turns the open web into an inspectable runtime for agents.

The browser connector is Scout's widest lens, but its job is not to impersonate a human browsing session. It creates a controlled chamber where pages can be opened, inspected, driven, and verified without inheriting personal state by accident.

Its identity is the instrumented window: familiar web surfaces on top, protocol machinery underneath, and a steady feedback loop between what the agent sees and what it does next.

State

clean sessions

Signal

CDP events

Loop

observe, act, verify

Related runtime

Real browser state belongs to the extension path

The public browser connector is the default automation path. When a workflow needs your real Chrome tabs, cookies, and operator-visible state, move to the Scout extension instead of stretching the hosted connector past its boundary.

Use the hosted browser connector for isolated runs, scraping, testing, and reproducible automation.

Use the extension app path only when the agent genuinely needs your existing browser session.

Do not treat the extension as another MCP server config. It has its own app runtime and provider-key setup.

Best for

Navigation, extraction, screenshots, forms, downloads, cookies, and network-aware automation.

Clean hosted browser sessions that should not inherit your personal Chrome profile.

Agent workflows that need the broadest Scout tool surface in one connector.

Runtime model

Runs clean connector-managed browser sessions backed by CDP-aware runtime ownership.

Can launch, attach, inspect, and coordinate sessions without assuming an existing personal browser context.

Keeps browser automation as one connector surface inside the wider Scout platform instead of standing in for the entire product.

Auth model

Use OAuth by default for interactive MCP clients and operator workstations.

Switch to Scout access tokens only for CI, scheduled jobs, or other environments that cannot open browser sign-in.

Credits and budget limits are checked at the connector boundary before longer browser runs continue.

Capability atlas

A compact map of what this connector can do.

Browser exposes 69 commands across 12 capability groups. The full reference stays close, while this page keeps the connector's runtime shape easy to understand.

Session

Manage browser sessions, tab attachment, and multi-agent coordination.

browser-tabsbrowser-attachbrowser-detachbrowser-launchbrowser-openbrowser-closebrowser-connectbrowser-disconnect+5 more

Navigation

Navigate between pages, manage browser history, and handle iframes.

browser-navigatebrowser-searchbrowser-historybrowser-stillbrowser-framesbrowser-wait

Content

Read and understand page content — snapshots, extraction, JavaScript evaluation.

browser-snapshotbrowser-extractbrowser-evaluatebrowser-pipebrowser-findbrowser-injectbrowser-tools

Interaction

Simulate user interactions — clicks, keyboard input, form filling, drag-and-drop.

browser-interactbrowser-selectbrowser-uploadbrowser-dialogbrowser-highlight

Network

Monitor network traffic, intercept requests, record HAR files, manage certificates.

browser-networkbrowser-routebrowser-unroutebrowser-harbrowser-securitybrowser-notificationsbrowser-notifybrowser-websocket

Storage

Manage cookies, localStorage, sessionStorage, and clipboard.

browser-cookiesbrowser-storagebrowser-clipboard

Media

Capture screenshots, record screencasts, manage downloads, control media playback.

browser-screenshotbrowser-pdfbrowser-screencastbrowser-mediabrowser-downloadbrowser-transcribe

Debug

Inspect console output, measure performance, monitor DOM memory stats.

browser-consolebrowser-metricsbrowser-memorybrowser-connect

Emulation

Emulate devices, geolocation, vision deficiencies, and network/CPU throttling.

browser-emulatebrowser-resizebrowser-visionbrowser-cpubrowser-throttlebrowser-pinch

Automation

High-level multi-page workflows and batch operations.

browser-batchbrowser-workflowbrowser-crawlbrowser-taskbrowser-channelbrowser-animation

Styling

Inspect and manipulate CSS computed styles.

browser-stylesbrowser-scroll

Payment

Manage wallet-backed asset balances, make payments for gated resources, and transfer supported assets between addresses.

payment-balancepayment-paypayment-transfer

Connection

Add the connector deliberately.

Add the hosted connector endpoint your MCP client needs. Each public connector stays separate so agent permissions and runtime boundaries remain explicit.

SnippetJSON

{
  "mcpServers": {
    "scout-browser": {
      "type": "http",
      "url": "https://mcp.scout.i.ng/browser"
    }
  }
}

Keep connector boundaries intentional

Dedicated connector pages should make capability boundaries memorable before the agent ever receives tools.

Browse all connectors Back to docs reference