Connect once, drive everything
Add the MCP server and an agent reaches browsing, profile lifecycle, fleet control and workflow recording. Raw CDP underneath, and your existing scripts still fit.
40+ tools across four families
Browser control, profile lifecycle, fleet control across many profiles at once, and workflow recording. An agent can create a profile, launch it, browse, act and save the run as a workflow without leaving the MCP session.
Two transports, on your terms
Local stdio runs with zero setup. Expose HTTP only when you choose, bound to localhost behind a 32+ character bearer token.
Your scripts still fit
Launching a profile returns a WebDriver driver path and the CDP endpoint, so existing Selenium, Puppeteer and Playwright scripts attach unchanged.
Raw CDP, no injected globals
The MCP path speaks raw Chrome DevTools Protocol to Oculr's own engine, so no Playwright or Puppeteer globals ever touch the page. Page structure is compressed 5 to 10x before it reaches the model, and a fingerprint regression gate re-checks the native surfaces after attach.
- No injected automation frameworks
- Snapshots compressed 5 to 10x
- Works with Claude and any MCP client
- Fingerprint regression gate on attach
One agent, the whole fleet
Fleet tools fan a single agent out across many region-pinned profiles at once. Launch, navigate, act and screenshot, each profile keeping its own identity.
One server, the whole browser surface
Connect over MCP and an agent reaches browsing, profile lifecycle, fleet control and workflow recording. Underneath it is raw CDP against Oculr's own engine, so nothing leaks the fact that automation is in play.
40+ tools across four families
The tool surface spans browser control, profile lifecycle, fleet control across many profiles at once, and workflow recording. An agent can create a profile, launch it, browse, act, and save the run as a workflow without leaving the MCP session.
- Browser, profile, fleet and recording tools
- Works with Claude and any MCP-compatible client
- Snapshots compressed 5 to 10x to save tokens
Two transports, on your terms
Local stdio runs with zero setup on your own machine. When you choose to expose the server over HTTP, it stays bound to localhost and requires a bearer token of at least 32 characters, compared in constant time.
- Local stdio for zero-setup local use
- HTTP bound to localhost, 32+ char bearer token
- Constant-time token comparison
Raw CDP, and your scripts still fit
The MCP path speaks raw Chrome DevTools Protocol by design, so no Playwright or Puppeteer globals ever touch the page. Launching a profile also returns a WebDriver driver path and CDP endpoint, so existing Selenium, Puppeteer and Playwright scripts attach unchanged, alongside a local REST API.
- No injected automation frameworks
- Selenium, Puppeteer and Playwright attach unchanged
- Local REST API for profile CRUD, launch and health
Frequently asked questions
What is the Oculr browser MCP server?+
It is a Model Context Protocol server that exposes Oculr's browser to any MCP-compatible client. Add it once and an agent can control the browser, manage profiles, drive a fleet, and record workflows through standard MCP tool calls.
What can the MCP tools do?+
40+ tools sit across four families: browser control (navigate, snapshot, click, type, evaluate, screenshot, tabs, dialogs, network log), profile lifecycle (create, launch, attach, inspect, update, stop, delete, list), fleet control across many profiles at once, and workflow recording.
Which transports does the MCP server support?+
Two. Local stdio runs with zero setup on your own machine. HTTP is available when you choose to expose it, bound to localhost and requiring a bearer token of at least 32 characters, compared in constant time.
Does Oculr inject Playwright or Puppeteer?+
No. The MCP path speaks raw Chrome DevTools Protocol to Oculr's own engine, by design, so none of the globals those frameworks add ever touch the page and undermine the engine's native-getter consistency.
Can I keep using my existing automation scripts?+
Yes. Launching a profile returns a WebDriver-compatible driver path and the CDP websocket endpoint, so existing Selenium, Puppeteer and Playwright scripts attach unchanged. There is also a local REST API for profile CRUD, launch and health.
How does it keep agent token use down?+
Page structure is compressed 5 to 10x before it reaches the model, so an agent spends tokens on decisions instead of raw DOM dumps. A fingerprint regression gate on the MCP path re-checks the native surfaces after attach.
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