Scout connector docs
Scout exposes capability-owned MCP servers that MCP clients can make available to the agent running inside them. Public connectors like browser, canvas, Figma, Node, system, and payment stay separate, while the extension follows its own app path.
A connector platform for AI agents
Scout is a connector platform with capability-owned MCP servers. MCP clients expose the selected connector tools to the agent running inside the client.
Public connectors like browser, canvas, Figma, Node, system, and payment stay separate so the agent only gets the capabilities the workflow actually needs.
The extension has its own app path and bundled tool surface; it is not configured as another public connector server.
Each connector owns its capability boundary, server endpoint, tool catalog, and runtime adapter.
The shared connector runtime handles auth, request identity, credit hydration, and streamable HTTP MCP transport.
MCP clients or Chrome extension
Scout has two setup paths: public MCP connectors for external clients, and the extension app path for real-browser workflows.
IDE and CLI MCP clients install or configure only the public connectors their agent needs, then authenticate with OAuth or a Scout access token.
The extension uses Scout's app flow and its own built-in tool surface for real-browser workflows.
Extension users provide an AI provider or gateway key in settings so Scout can route model requests.
Choose the client path, then configure it
Start by choosing the client path you are actually using. MCP clients need connector server configuration and auth; the Chrome extension needs the app install and a provider key.
For Claude Code, IDE agents, or CLI harnesses, install or configure only the connectors the agent needs for that workflow, such as browser, Node, system, canvas, Figma, or payment.
For normal MCP clients, use OAuth by default and create Scout access tokens only for CI, scheduled jobs, and non-interactive MCP clients.
For the Chrome extension, add the AI provider key from the model provider you want to use; do not copy MCP server configs into the extension.
Verify MCP-client connections with tool discovery before attempting longer automations.
Choose your browser path
Pick the browser context your workflow actually needs before you wire an MCP client.
Hosted browser connector
The default browser-automation path. Configure the browser MCP server in your client, authenticate, and let Scout run browser automation through that connector.
Clean connector-managed browser sessions. No extension. No existing cookies or tabs unless the workflow attaches to a chosen browser target.
IDE agents that need a standard MCP server
CI, scheduled jobs, scraping, and isolated runs
Automation that should not inherit your personal browser state
An MCP-compatible client
The public browser connector endpoint at https://mcp.scout.i.ng/browser
OAuth for normal use, or a Scout access token only when browser-based auth is impossible
Chrome extension app
The app path. The extension uses Scout's built-in runtime to operate your real browser with the AI provider key you supply.
Your real Chrome session via the Scout extension and Scout's app-side runtime.
Workflows that require your real logged-in browser
Using existing tabs, sessions, cookies, and extension state
Operator-style tasks where the browser should remain visible and persistent
The Scout Chrome extension
A connection to Scout's app runtime
An AI provider or gateway API key in extension settings
A workflow that explicitly benefits from existing authenticated browser state
Connector server setup
Configure the hosted browser connector, authenticate, then verify the tool catalog with a small real call.
Client
Cursor
Connect Cursor to Scout's hosted browser connector, complete browser-based OAuth, and verify the tool catalog before you start using Scout in chat.
Add the Scout browser connector entry to .cursor/mcp.json.
Save the file and let Cursor reload the MCP configuration.
Choose the Scout server when Cursor prompts to connect.
SnippetJSONCursor should open the browser sign-in flow automatically on first connect. Complete the OAuth prompt, then return to Cursor and confirm the Scout server appears under MCP tools.
Open Cursor Settings > Tools & MCP and confirm the Scout server is connected.
Ask Cursor: "List the Scout MCP tools available in this workspace."
Run a low-risk verification task such as: "Use Scout MCP tools to open example.com and snapshot main."
Access tokens
Use Scout access tokens only for clients and jobs that cannot complete browser-based OAuth.
When to use access tokens
Use browser-based OAuth for normal interactive setup. Switch to access-token authentication only when your client cannot complete the sign-in flow or when you need non-interactive automation.
Prefer OAuth discovery for local development and everyday IDE use.
Use a Scout access token only for CI, scheduled jobs, or MCP clients without browser-based OAuth.
Keep the token scoped to the narrowest environment you can tolerate, ideally development or staging.
Revoke the token when the integration or job no longer needs it.
CI and headless automation
For CI or headless automation, attach a Scout access token as the Authorization header. This keeps the transport the same while bypassing browser-based login.
Generate a Scout access token from the Scout account UI or token management flow.
Store it in your CI secret store instead of committing it to the repo.
Inject it into the MCP client config as a Bearer header at runtime.
Rotate or revoke it after the automation job, especially for temporary workflows.
Programmatic MCP clients
Programmatic MCP callers can also use a Scout access token when they cannot complete OAuth. The auth shape is the same once the request reaches Scout: a userId plus derived workerId, with tokenId included for token-based access.
Use OAuth-derived access tokens when you can.
Fall back to a Scout access token only when browser sign-in is impossible.
Keep the token in environment variables or your secret manager.
Verify the connection with listTools() before starting a long-running job.
Security recommendations
Keep capability, identity, and browser-state boundaries explicit.
Keep AI automation away from production by default
Do not default to production data when connecting an MCP client. Prefer development or staging environments, and keep real customer data away from exploratory AI workflows whenever possible.
Review tool calls, especially after reading untrusted content
Leave manual approval enabled in your MCP client and review tool calls before execution. Prompt injection remains a real risk whenever the model can read untrusted page content and then decide what to run next.
Use the right browser path for the risk level
Prefer hosted browser connector sessions for scraping, testing, and untrusted sites. Reserve the extension path for workflows where you explicitly want your real browser cookies, sessions, and authenticated state.
Treat access tokens like high-value secrets
Scout access tokens are powerful credentials. Store them in secret managers, scope them narrowly, rotate them when workflows change, and revoke them when an integration ends.
Constrain access rather than relying on the model to behave
Reduce the available action set when possible. Install or configure only the connector MCP servers needed for the workflow, and use the shortest-lived credential that still satisfies the automation.
Quickstart snippets
Small, copyable examples for the browser connector loop.
Access token for CI
SnippetJSONProgrammatic client fallback
SnippetTYPESCRIPTConnector reference
Verified against the registered connector handler surfaces so browser, payment, canvas, Figma, Node, and system all appear as first-class MCP servers.
Browser
mcp.scout.i.ng/browserBrowser automation remains the broadest connector surface, but it is one connector in the platform, not the platform itself.
Hover a command to preview what it does.
Session
13Manage browser sessions, tab attachment, and multi-agent coordination.
browser-tabsbrowser-attachbrowser-detachbrowser-launchbrowser-openbrowser-closebrowser-connectbrowser-disconnectbrowser-windowagent-messageagent-rosteragent-requestagent-respondNavigation
6Navigate between pages, manage browser history, and handle iframes.
browser-navigatebrowser-searchbrowser-historybrowser-stillbrowser-framesbrowser-waitContent
7Read and understand page content — snapshots, extraction, JavaScript evaluation.
browser-snapshotbrowser-extractbrowser-evaluatebrowser-pipebrowser-findbrowser-injectbrowser-toolsInteraction
5Simulate user interactions — clicks, keyboard input, form filling, drag-and-drop.
browser-interactbrowser-selectbrowser-uploadbrowser-dialogbrowser-highlightNetwork
8Monitor network traffic, intercept requests, record HAR files, manage certificates.
browser-networkbrowser-routebrowser-unroutebrowser-harbrowser-securitybrowser-notificationsbrowser-notifybrowser-websocketStorage
3Manage cookies, localStorage, sessionStorage, and clipboard.
browser-cookiesbrowser-storagebrowser-clipboardMedia
6Capture screenshots, record screencasts, manage downloads, control media playback.
browser-screenshotbrowser-pdfbrowser-screencastbrowser-mediabrowser-downloadbrowser-transcribeDebug
4Inspect console output, measure performance, monitor DOM memory stats.
browser-consolebrowser-metricsbrowser-memorybrowser-connectEmulation
6Emulate devices, geolocation, vision deficiencies, and network/CPU throttling.
browser-emulatebrowser-resizebrowser-visionbrowser-cpubrowser-throttlebrowser-pinchAutomation
6High-level multi-page workflows and batch operations.
browser-batchbrowser-workflowbrowser-crawlbrowser-taskbrowser-channelbrowser-animationStyling
2Inspect and manipulate CSS computed styles.
browser-stylesbrowser-scrollPayment
3Manage wallet-backed asset balances, make payments for gated resources, and transfer supported assets between addresses.
payment-balancepayment-paypayment-transferArchitecture notes
The small set of system concepts that actually change how you choose a path, authenticate, and operate Scout safely.
Connectors are configured separately so each workflow only exposes the capabilities it actually needs.
The extension follows Scout's app-side tool flow rather than appearing as another public connector users install directly.
Use the extension path only when the task depends on your real tabs, cookies, or authenticated browser state; otherwise keep the workflow on isolated connector sessions.
FAQ
Common questions about setup, authentication, browser state, security, and billing.