Integration Paths
CLI + SKILL.md
Best for coding agents with shell access. Install globally, run
bap install-skill, and your
agent learns browser commands automatically. bash npm i -g @browseragentprotocol/cli MCP Server
Best for tool-native MCP clients like Claude Code, Codex, and Cursor. Zero config — just add
the MCP server.
bash npx -y @browseragentprotocol/mcp TypeScript SDK
Best for apps and agent backends. Full programmatic control with semantic selector helpers.
bash npm i @browseragentprotocol/client Python SDK
Best for notebooks, Python agents, and data pipelines. Async and sync APIs available.
bash pip install browser-agent-protocol Prerequisites
- Node.js >= 20.0.0 (for CLI, MCP, and TypeScript SDK)
- Python >= 3.10 (for Python SDK only)
- Playwright browsers: Install with
npx playwright install chromium
Architecture
All four integration paths talk to the same BAP Playwright server:Why BAP
| Feature | What it means |
|---|---|
| Real browser | Prefers installed Chrome, keeps session state warm, behaves like a normal user browser |
| Semantic selectors | role:button:"Submit" and label:"Email" instead of brittle CSS |
| Fewer roundtrips | Fused operations like goto --observe and composite bap act reduce server calls |
| Warm daemon | Browser stays alive across commands — agents keep momentum |
| Token efficient | --slim mode exposes 5 tools (~600 tokens) vs 70+ in competitors (~4,200 tokens) |
| Multiple surfaces | CLI, MCP, TypeScript SDK, Python SDK — pick what fits your stack |
Quick Example
Next Steps
CLI Quickstart
Install and run your first commands
Selectors
Learn the 10 selector types
Fusion
Reduce roundtrips with fused operations
Workflows
Record and replay browser workflows