Dedicated pages for the connector surfaces Scout exposes publicly
Browser, canvas, Figma, Node, payment, and system are not footnotes under one giant browser product. They are separate public MCP connectors with different runtimes, setup paths, and operational boundaries.
Connector directory
Choose the smallest real surface your workflow needs, then wire only that connector into your MCP client.
Browser
69 commandsScout's browser connector is the broadest public surface: a hosted MCP server for clean browser sessions, CDP-backed automation, and multi-step web workflows.
Navigation, extraction, screenshots, forms, downloads, cookies, and network-aware automation.
Canvas
5 commandsCanvas is the connector for rendered surfaces that break normal DOM assumptions: frame diffs, WebGL state, and interaction sequences across canvas-based interfaces.
Canvas-heavy apps where DOM-level browser tools are not enough.
Figma
71 commandsScout's Figma connector pairs with a plugin-backed runtime so agents can inspect and mutate live files, components, variables, and exports through MCP.
Working against a live Figma file instead of static exports or screenshots.
Node
20 commandsNode is a public debugging and diagnostics connector for remote V8 inspection, runtime evaluation, breakpoints, tracing, and process-level analysis.
Attaching to Node or V8 runtimes for diagnostics and debugging.
Payment
5 commandsPayment is Scout's commerce connector: a dedicated surface for balances, challenge flows, payment execution, and money-moving workflows.
Balance checks, commerce flows, challenge handling, and payment execution.
System
14 commandsSystem is Scout's host-automation connector for apps, dialogs, clipboard, keyboard, mouse, windows, screenshots, and accessibility-aware desktop workflows.
Desktop automation and accessibility-aware host-machine workflows.