Skip to content

Getting started with Browserberg

Your first hour with Browserberg: create a key, run a session, install an SDK and connect the MCP server to a coding agent.

Four short pages take you from an empty account to a working integration. You will create an API key, drive one session end to end, pick a surface for your team — TypeScript, Python or raw HTTP — and, if you prefer, hand the whole browser to a coding agent over MCP. Start with the quickstart; the rest reads in order.

All pages in this section

  1. 1

    Quickstart: first session in five minutes

    Create an API key, start a hardened browser session, navigate deterministically and run one model-backed extraction, in about five minutes.

  2. 2

    Installation: SDKs and the raw HTTP surface

    Install the TypeScript or Python SDK or call the HTTP API directly, and learn what the protocol version header negotiates for you.

  3. 3

    Authentication: API keys and accounts

    How Browserberg separates machine keys from human dashboard accounts, how to create a bearer key, and how to read the error envelope.

  4. 4

    MCP server: a hosted browser for coding agents

    Connect Claude Code or any MCP client to Browserberg: a hosted endpoint, tools for browsing, delegated tasks, workflows and the audit log, plus a skill.