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.
Google ADK loads external tools through McpToolset. Point it at the Notte MCP server and your agent gets the full Notte toolset - sessions, browser agents, scraping, functions, vaults and personas - with no wrapper code to maintain.

Prerequisites

  • A Notte API key (get one here)
  • Credentials for the model your ADK agent uses

1. Install the SDKs

2. Attach the Notte MCP server

Notte’s MCP server speaks streamable HTTP and authenticates with a bearer token:
notte_google_adk.py
Set the following environment variable in your .env file:

Next steps

MCP Server

Every tool the Notte MCP server exposes

Browser Agents

Hand a whole task to a Notte agent

Vaults

Let agents log in without seeing credentials

Functions

Turn a working run into a callable function