Labsco
MCP SERVER · OFFICIAL PROJECT

Anchor Browser Automation

by Anchor (Agentic Browser Automation)

A hosted browser an agent drives — navigate, click, type, screenshot, run JavaScript, watch network traffic.

Browser Automation, Control & ScreenshotsOfficial source
Summary
Metered by browser-hour, which changes how you write the automation.

Local browser servers fail in the sandbox because there is no Chrome; this one fails only if you run out of credit. That is the trade: reliability for a meter that runs while the browser is open. Write flows that close tabs and finish, not ones that leave a session parked. The network-requests tool is the sleeper — most browser MCPs give you a screenshot of a broken page and nothing about the failed request behind it.

What it is

Anchor runs the browsers; you send an API key in a header and drive them over MCP. There is no Chrome to install and no driver to keep alive.

What you get
  • Navigation, clicking, typing and waiting for conditions
  • Accessibility-tree snapshots and screenshots — the snapshot is what an agent should read, the screenshot is for you
  • Tab management: open, list, switch, close
  • File upload, dialog handling, PDF generation
  • Network request inspection, which is how you find out why a page did not load
Requirements

An API key in the anchor-api-key header. Free gives $5 of credits a month and up to five concurrent browsers; Starter is $50/mo. Infrastructure meters separately — $0.01 per browser created, $0.05 per browser-hour, $8/GB through their proxy.

Setup effort

Paste a URL with a key — add the endpoint to your client