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.
The Vercel AI SDK can load tools from an MCP server and pass them straight into generateText or streamText. Point its MCP client at the Notte MCP server and your TypeScript agent gets 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:
The MCP client lives in @ai-sdk/mcp. Older guides import experimental_createMCPClient from ai itself, which no longer exports it.

Next steps

MCP Server

Every tool the Notte MCP server exposes

Connect with Puppeteer

Drive a Notte session from Node.js over CDP

Browser Agents

Hand a whole task to a Notte agent

Fetch

Pull structured data out of a page