Extension connectorMCP-first

Extension runtime automation as its own connector

Extension is Scout's connector for sideloading and automating unpacked Chrome extensions: launch, background workers, storage, and reload loops for development workflows.

launchopenbackgroundreload

See connector reference Browse connectors

The extension workbench

Warm gold chrome, service-worker consoles, reload rails, and a dev-loop energy that treats the extension itself as the instrument under test.

A workbench around an unpacked extension: sideloaded packages, background workers, extension pages, and storage panels laid out for rapid development loops.

Identity

Extension is the connector for building and driving extension runtimes, including Scout itself.

A Chrome extension is its own small runtime: a background worker, UI pages, storage surfaces, and a lifecycle that only makes sense while it is running.

This connector gives agents a developer-shaped relationship with that runtime: sideload, launch, evaluate, reload, so extension work becomes a named surface instead of bespoke browser scripting.

State

service worker

Signal

extension storage

Loop

launch, evaluate, reload

Related runtime

Real browser state belongs to the extension path

The extension is the runtime where an agent can reach your real Chrome state. When a workflow genuinely needs your existing tabs, cookies, and operator-visible sessions, the extension app path is the boundary, not the hosted browser connector.

Use the hosted browser connector for isolated, reproducible automation.

Use the extension path when the agent needs your real browser session.

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

Best for

Sideloading and automating an unpacked Chrome extension during development.

Driving the background service worker, opening extension pages, and reading or writing extension storage.

Reload loops that let agents iterate quickly on extension behavior and UI.

Runtime model

Sideloads and automates unpacked Chrome extensions, including the Scout extension itself.

Drives background workers, extension pages, and storage surfaces as first-class runtime state.

Keeps extension development inside a named connector instead of one-off browser scripting.

Auth model

The extension connector runs through the Scout extension app path rather than a separate OAuth sign-in.

Add the AI provider or gateway key you want Scout to use inside the extension itself.

The public endpoint exposes extension development tools for sideloaded unpacked extensions.

Capability atlas

A compact map of what this connector can do.

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

Extension

Sideload an extension, open its pages, drive the background worker, manage storage, and reload.

extension-launchextension-openextension-backgroundextension-reloadextension-storage

Authentication

Authenticate with a bearer token.

Every Scout connector accepts a bearer token in the Authorization header. Sign in to your Scout account and create an MCP token from the MCP Tokens page, then paste it into your MCP client config.

Create MCP token Learn about auth

SnippetJSON

{
  "mcpServers": {
    "scout-browser": {
      "type": "http",
      "url": "https://mcp.scout.i.ng/browser",
      "headers": {
        "Authorization": "Bearer <mcp-token>"
      }
    }
  }
}

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