Agents fail in browsers built for scripts
Generic automation stacks announce themselves to every site they touch. Oculr gives your agent the same thing a person has: a real browser with a consistent identity.
One command connects your agent
Oculr ships a Model Context Protocol server with 40+ tools across browsing, profile lifecycle, fleet control and workflow recording. Local stdio for zero setup, or HTTP with mandatory bearer-token auth.
- Works with Claude and any MCP client
- Raw CDP underneath, no Playwright or Puppeteer globals
- Snapshots compressed 5 to 10x to save tokens
A browser the page treats as a browser
Fingerprinting is built into Oculr's own Chromium engine at the engine level, not patched on with JavaScript. Detection-relevant getters return the same native code signatures stock Chrome returns, and every release is regression-tested against public fingerprint suites.
- Engine-level fingerprinting, not JS patches
- One profile, one consistent identity
- Timezone, language and location re-apply on every tab
From one profile to a fleet
Fleet commands let one agent drive many profiles at once: launch, navigate, click, type and screenshot across the set, while each profile keeps its own proxy, storage and fingerprint.
- Drive 5, 10 or 50 profiles in one call
- Per-profile proxies and identities throughout
- Run a task once, replay it as a workflow
One connection. Forty tools. Your agent.
Add Oculr as an MCP server and your agent gains a full browser control plane: real Chromium, raw CDP, and fleet commands, all in one place.
Connect once, then just ask
Local stdio for zero setup, or HTTP with mandatory bearer-token auth. Raw CDP underneath, so no Playwright or Puppeteer globals ever touch the page.
Tools across four families
Browsing, profile lifecycle, fleet control and workflow recording, all exposed to your agent.
Tokens spent on decisions
Page structure is compressed before it reaches the model, so the agent spends tokens on decisions instead of raw DOM dumps.
One agent, the whole fleet
One MCP call fans out across many region-pinned profiles, each keeping its own proxy, cookies and fingerprint.
Frequently asked questions
Which AI agents work with Oculr?+
Any MCP-compatible client: Claude Code, Claude desktop, or your own agent built on the Model Context Protocol. Add Oculr as an MCP server and the agent can create profiles, browse, and run workflows.
Does Oculr inject Playwright or Puppeteer into the page?+
No. Oculr speaks raw Chrome DevTools Protocol to its own engine, so none of the globals those frameworks add ever touch the page. Your existing Selenium, Puppeteer and Playwright scripts can still attach through the standard endpoints.
Why do agents need an antidetect browser at all?+
Sites treat generic automation environments differently from real browsers. Oculr profiles are real Chromium with consistent, engine-level identities, so your agent sees the same site a person would, in a stable environment you control.
How do agents handle pages without burning tokens?+
Oculr compresses page structure 5 to 10x before it reaches the model, so the agent spends tokens on decisions instead of raw DOM dumps.
Can one agent drive many profiles at once?+
Yes. Fleet commands let an agent create, launch, navigate and act across many profiles in a single call, each profile keeping its own proxy, cookies and fingerprint.
Give your agents a browser that sites trust
Spin up your first two profiles free. Point an agent at them, run a task, and watch Oculr turn it into a workflow you can scale.
No credit card required · Cancel anytime