# Oya Browser

> Oya Browser is a freemium MCP server for browser automation. HIPAA-oriented agentic browser with replayable playbooks, reachable over MCP. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Pricing:** Freemium
- **Starting price:** $20 a month
- **Platforms:** macOS, Windows, Linux, API, CLI, self-hosted
- **Website:** https://oyabrowser.com
- **Repository:** https://github.com/oyadotai/oya-browser
- **GitHub stars:** 349
- **MCP Registry name:** io.github.OyadotAI/oya-browser
- **Categories:** browser automation, health and science
- **Listing updated:** 2026-11-14

## About

Oya Browser is a browser control plane aimed at healthcare and other regulated work. It offers a desktop AI browser and an agentic browser that agents can run in Oya Cloud or on your own infrastructure, with each action written to a tamper-evident audit trail.

Over MCP, an agent can browse, run saved playbooks, or hand a tab to a person. A task is described once, Oya records the agent's portal actions, and the steps are saved as readable Playwright code with variable inputs that can be replayed through the SDK without a model.

It targets healthtech and revenue-cycle teams that automate payer-portal tasks such as prior authorizations. The vendor says it signs BAAs, and that its SOC 2 Type II audit is in progress.

## Features

- **Record and replay playbooks:** A first task is recorded and saved as Playwright code with variable inputs for later runs.
- **MCP access:** Agents can browse, run playbooks and hand a tab to a human through a remote MCP endpoint.
- **Audit trail:** Every action is logged on a tamper-evident audit trail.
- **Cloud or self-hosted:** Browsers can run in Oya Cloud or be self-hosted so pages and recordings stay in your network.
- **Desktop browser:** An AI browser app runs on the desktop for individual use.
- **Model-free replay:** Saved workflows can be called through the SDK without calling a language model.

## Good for

- Submit prior authorization requests in payer portals
- Automate repetitive healthcare portal data entry
- Run regulated browser workflows with an audit record
- Hand a browser tab to a person mid-task
- Replay saved workflows with new case details

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http oya-browser https://oyabrowser.com/mcp/pool
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://oyabrowser.com/mcp/pool
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "oya-browser": {
      "url": "https://oyabrowser.com/mcp/pool"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "oya-browser": {
      "type": "http",
      "url": "https://oyabrowser.com/mcp/pool"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "oya-browser": {
      "serverUrl": "https://oyabrowser.com/mcp/pool"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "oya-browser": {
      "type": "http",
      "url": "https://oyabrowser.com/mcp/pool"
    }
  }
}
```

## Tools

- `select_option`: Choose an option in a native dropdown (a select element from analyze_page) by the option text you see. Accepts {{placeholders}} and filters.
- `run_script`: Run JavaScript that READS the page and returns data, for what analyze_page does not show well: every row of a long table, attributes, counts, text across many elements. The body of an async function: `return` the value (JSON-serialisable, cut at 8000 chars). It runs where the page cannot see it and must not change anything: no clicks, typing, requests or navigation; act with the element tools, whi
- `wait_for`: Wait until the page is ready: some text shows, the url contains something, and/or the network has gone quiet. With no text or url it waits for the network to settle. Use it after an action that loads results in the background, rather than analyzing again and again.
- `find`: Find the elements that match a description ("search box", "add to cart", "next page"), best first, with ids click and type accept. Much shorter than analyze_page when you know what you are looking for.
- `hover`: Move the mouse onto an element, for menus, tooltips and previews that open on hover. Tells you what appeared.
- `go_back`: Go back one page in the tab's history, like the browser's back button, and wait for it to load.
- `go_forward`: Go forward one page in the tab's history and wait for it to load.
- `reload`: Reload the page and wait for it to load. For a page stuck loading or showing stale data.
- `solve_captcha`: Solve a CAPTCHA (reCAPTCHA, hCaptcha, Turnstile) on the current page with the configured solver. Call it when a CAPTCHA blocks you, then analyze_page again.
- `sign_in`: Sign in on the current page with the credentials stored for this site in the browser's persona. You never see them. Call it on a login form you were not given values for.
- `complete_mfa`: Fill and submit a one-time code (MFA / 2FA) the page asks for, from the persona's authenticator, email or SMS. Call it on a code prompt after signing in.
- `list_saved_logins`: List the sites this browser's persona has a saved login for, with the username, never the password. Call it before a sign-in to know whether sign_in can fill the form and which account it will use.
- `list_playbooks`: List the playbooks saved on this key: recorded flows that replay without a model, with their variables.
- `run_playbook`: Replay a saved playbook on this browser with the given variables. Much faster and cheaper than doing the task step by step; a step that no longer fits the page is finished by the agent.
- `run_task`: Hand a whole task to Oya's own browser agent on this browser and get its report back (DONE: or FAILED:). Uses this key's configured model; the run can be saved as a playbook afterwards.
- `analyze_page`: Analyze the current page. Returns its content and every interactive element with an id to use with click/type tools. Ids stay valid until the next analysis or a navigation, so one analysis covers a whole form; each analysis numbers the page afresh. plus page facts (url, title, viewport, scroll, and when they apply: panelScroll, modal, covered, truncated) and each element's state (off-screen, disab
- `navigate`: Navigate the browser to a URL.
- `click`: Click an interactive element by its ID number (from analyze_page results).
- `type`: Type text into an input element by its ID number (from analyze_page results). Clears existing content first. Typing keeps every id valid: fill the next field straight away, without analyzing again.
- `screenshot`: Capture a screenshot of the visible browser tab as an image.
- `press_key`: Press a safe navigation key. Allowed: Enter, Escape, Tab, ArrowDown, ArrowUp, ArrowLeft, ArrowRight, Backspace, Delete, Space, Home, End, PageUp, PageDown. Do NOT use for F-keys, Meta, Control, Alt, or Shift.
- `handle_dialog`: Answer a native browser dialog (confirm or prompt) blocking the page. Alerts are answered automatically.
- `scroll`: Scroll the page up or down.
- `wait`: Wait for an element matching a CSS selector to appear on the page.
- `click_coordinates`: Click at specific x,y pixel coordinates on the page. Use when you know the exact position (e.g. from a screenshot).
- `mouse_move`: Move the mouse cursor to specific x,y coordinates without clicking. Useful for triggering hover states, tooltips, or dropdown menus.
- `double_click`: Double-click an element by ID or at specific x,y coordinates.
- `keyboard_type`: Type text using the keyboard without targeting a specific element. Types into whatever is currently focused.
- `drag`: Drag from one point to another. Useful for sliders, drag-and-drop, or selecting text.
- `start_browser`: Start a new browser on this key and make it the one every other tool drives. Uses the key's configured provider unless one is given. It costs a session until stop_browser.
- `stop_browser`: Stop a browser and release its session. Defaults to the browser the tools are driving.
- `pool_status`: Show pool size and connected browsers.

## FAQ

### Does Oya sign a BAA?

Yes, the vendor says it signs BAAs, and that its SOC 2 Type II audit is in progress.

### Can it be self-hosted?

Yes. Self-hosted browsers keep pages, recordings and audit records in your network.

### How much does it cost?

The desktop app and 500 agent steps a month are free. Oya Cloud Developer is $20 a month and Startup is $99 a month.

### Which model keys are needed?

Natural-language tasks need an Anthropic, OpenAI or Gemini API key.

### Is Oya Browser free?

Oya Browser has a free plan, with paid plans for more usage or features. Paid plans start at $20 a month.

### How do I add Oya Browser to Claude Code?

Run this command in your terminal: claude mcp add --transport http oya-browser https://oyabrowser.com/mcp/pool

### What are the best alternatives to Oya Browser?

The closest alternatives to Oya Browser are Browser Use, Scrapling MCP Server, Tooluniverse, Mantis and Later Stages.

## Alternatives

- [Browser Use](https://ai-powered.com/mcp/browser-use): Browser Use is a freemium MCP server for browser automation.
- [Scrapling MCP Server](https://ai-powered.com/mcp/scrapling-mcp-server): Scrapling MCP Server is an open-source MCP server for web search and scraping.
- [Tooluniverse](https://ai-powered.com/mcp/tooluniverse): Tooluniverse is an open-source MCP server for health and science.
- [Mantis](https://ai-powered.com/mcp/mantis-2): Mantis is an open-source MCP server for browser automation.
- [Later Stages](https://ai-powered.com/mcp/later-stages): Later Stages is a free MCP server for health and science.
- [MedXpert 标准检索连接器](https://ai-powered.com/mcp/medxpert-2): MedXpert 标准检索连接器 is a free MCP server for legal and government.
- [MedXpert 全球法规连接器 (reg-connector)](https://ai-powered.com/mcp/medxpert-reg-connector): MedXpert 全球法规连接器 (reg-connector) is a free MCP server for legal and government.
- [Splyt](https://ai-powered.com/mcp/splyt): Splyt is a free MCP server for health and science.

---
Source: https://ai-powered.com/mcp/oya-browser
