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.
Agno ships an MCPTools toolkit that connects an agent to any MCP server. Point it at the Notte MCP server to give your agent sessions, browser agents, scraping and functions.

Prerequisites

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

1. Install the SDKs

2. Attach the Notte MCP server

notte_agno.py
Set the following environment variable in your .env file:
Pass the bearer token through header_provider, not headers - MCPTools forwards header_provider to the HTTP transport and rejects a bare headers argument.

Next steps

MCP Server

Every tool the Notte MCP server exposes

Browser Agents

Hand a whole task to a Notte agent

Fetch

Pull structured data out of a page

Functions

Turn a working run into a callable function