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.
Give your AI agents access to the entire Notte ecosystem. Notte MCP lets it start cloud browser sessions, interact with the pages, fetch data, build scripts, and more.

Add the Notte MCP

Create a Notte API key and connect your client to the hosted MCP endpoint:
Run this command and verify the connection with claude mcp list

Post setup verify

Run this prompt in your assistant to check that setup is all good:

Notte Documentation MCP

You can also configure the Notte Docs MCP to give your coding agent current documentation while it helps you build. It needs no API key.
Run this command and verify the connection with claude mcp list