Canvas connectorMixed MCP + CDP

Canvas workflows without DOM guesswork

Canvas is the connector for rendered surfaces that break normal DOM assumptions: frame diffs and point-based interaction across canvas-based interfaces.

sampledifftraceinteract
See connector referenceBrowse connectors
The pixel instrument

Pixel grids, frame deltas, cursor paths, and luminous geometry for interfaces that hide their truth behind a bitmap.

A rendered field where pixels, vectors, and interaction points become addressable. The visual language is a live raster grid of pixels.

Identity

Canvas gives agents a way to work where the DOM stops telling the truth.

Canvas-heavy products are often visually rich and structurally opaque. Their meaning lives in pixels, transforms, and point-based interactions instead of semantic DOM nodes.

This connector treats rendered space as a first-class medium. It can inspect, compare, and act against the surface the user actually sees.

State

rendered frames

Signal

pixel deltas

Loop

sample, compare, interact

Best for

Canvas-heavy apps where DOM-level browser tools are not enough.

Pixel comparison and frame diffing.

Point-based interaction inside design tools, editors, maps, and games.

Runtime model

Focuses on rendered surfaces that do not expose their real state cleanly through the DOM.

Pairs canvas inspection and diffing with point-based interaction, rather than pretending every app is a form-and-button website.

Lets the agent target canvas surfaces as a first-class runtime, not as an afterthought of browser automation.

Auth model

Connect the canvas endpoint through the same Scout account boundary as other public connectors.

Use OAuth for normal interactive setup and Scout MCP tokens only when browser sign-in is impossible.

Keep canvas access separate from browser and system capabilities unless the workflow explicitly needs all of them.

Capability atlas

A compact map of what this connector can do.

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

Content

2

Inspect canvas state and compare frames.

canvas-diffcanvas-inspect

Interaction

1

Drive point-based interaction inside a canvas surface.

canvas-interact
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 tokenLearn 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 connectorsBack to docs reference