Oculr API
The Oculr API is a local HTTP API that launches browser profiles on your own hardware and hands you a CDP endpoint you can drive with Playwright, Puppeteer, Selenium, or MCP.
Overview
Oculr exposes a small HTTP API that runs on the same machine as the app. You ask it to launch a profile, it returns a ready Chrome DevTools Protocol (CDP) endpoint, and you connect any standard automation driver to that endpoint. The profile carries its own fingerprint, storage, and proxy, so each session looks like an ordinary browser on an ordinary device.
The browsers run on hardware you own, either locally or on a server you host. Nothing is rendered in a metered cloud, so there is no per browser hour charge for the sessions themselves.
- Launch a profile over HTTP and receive a CDP endpoint.
- Connect Playwright, Puppeteer, Selenium, or the MCP server to that endpoint.
- Drive the page with the driver you already know.
- Reuse the same profiles from scripts, the MCP server, and the built in agent.
Base URL and token
The API is served by the local Oculr agent. The default base URL looks like http://127.0.0.1:8378. The app shows the exact port and the access token under Settings, so copy both from there rather than hard coding them.
http://127.0.0.1:8378/apiHow it fits together
Every entry point talks to the same local API and the same CDP sessions. A Node script, a Python script, the MCP server, and the built in agent all launch the same profiles and attach over the same protocol. There is no separate automation layer to learn for each one.
| Entry point | How it connects |
|---|---|
| REST scripts | POST a launch, then attach a driver to the CDP endpoint |
| MCP server | profile_* and browser_* tools over the same API |
| Built in agent | natural language and recorded workflows over the same profiles |