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.
crewAI gives every agent in a crew a set of tools. MCPServerAdapter turns an MCP server into those tools, so pointing it at the Notte MCP server hands your crew a real browser.

Prerequisites

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

1. Install the SDKs

2. Attach the Notte MCP server

notte_crewai.py
Set the following environment variable in your .env file:
MCPServerAdapter is a context manager. Build your crew inside the with block so the tools stay connected for the whole run.

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

Personas

Give each agent its own identity and inbox