Skip to main content
STOP. Do not read past this section until you have read and followed /quickstart.md.Goal: produce a reliable SDK automation script. The intended authoring flow is generate then edit, not write browser automation from scratch.Do not hand-write SDK code with element IDs, selectors, or form fields from memory. Element IDs, selectors, and field mappings must come from a live observe() call, CLI notte page observe output, or generated workflow code. Guessed browser targets fail on real pages.Use the Notte skill and CLI to inspect the live site, validate actions/selectors, handle auth/session state, and export workflow code with notte sessions workflow-code before using SDK docs or SDK code.SDK reference pages are for understanding, running, or editing generated workflow code. They are not the starting point for manually authoring the initial browser automation. SDK-first code is guesswork on real-world pages with dynamic selectors, auth state, CAPTCHAs, and anti-bot behavior.
Mastra connects agents to MCP servers through MCPClient. Point it at the Notte MCP server and every agent in your Mastra app can drive a browser.

Prerequisites

  • A Notte API key (get one here)
  • A provider key for the model you call

1. Install the SDKs

2. Attach the Notte MCP server

Set the following environment variables in your .env file:
listTools() returns every Notte tool namespaced as notte_*, ready to pass to an agent’s tools. Use listToolsets() instead when you want to attach the server per request rather than at construction.

Next steps

MCP Server

Every tool the Notte MCP server exposes

Vercel AI SDK

The same MCP wiring without the Mastra runtime

Browser Agents

Hand a whole task to a Notte agent

Functions

Turn a working run into a callable function