Canvas connectorMixed MCP + CDP

Canvas and WebGL workflows without DOM guesswork

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

sampledifftraceinteract

See connector reference Browse 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 bending toward a WebGL plane.

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, frame diffing, and WebGL-aware inspection.

Point-based interaction playback 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 and WebGL 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 access tokens only when browser auth is impossible.

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

Capability atlas

A compact map of what this connector can do.

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

Content

Inspect canvas state, compare frames, and capture WebGL-level state.

canvas-diffcanvas-inspectcanvas-webgl

Interaction

Drive point-based interaction and ordered workflows inside a canvas surface.

canvas-interactcanvas-sequence

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-canvas": {
      "type": "http",
      "url": "https://mcp.scout.i.ng/canvas"
    }
  }
}

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