A browser MCP server agents can drive
Oculr ships a Model Context Protocol server with 40+ tools across browsing, profiles, fleets and recording. Two transports, your agent talking straight to the browser over Chrome's own DevTools Protocol (CDP), and your existing automation scripts attach without changes.
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 browser MCP 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, with none of the extra globals Playwright or Puppeteer inject into the page.
The server implements the Model Context Protocol, the open standard for giving models tools, so Claude or any MCP client can drive a real browser through standard tool calls. Each profile is driven over raw CDP with no injected automation frameworks, on the same native antidetect engine the rest of Oculr runs on. It is the browser layer behind AI agents and automation, and your existing Selenium, Puppeteer and Playwright scripts still attach unchanged.
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 agent the whole browser over MCP
Spin up your first two profiles free, add the MCP server in one line, and let an agent drive browsing, profiles and fleets through 40+ tools.
No credit card required · Cancel anytime