# Oya Browser

Gives your agent a real Chrome: opens pages, reads them as numbered markdown, clicks and types. You watch the run and can take control.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 351
- Author: OyadotAI
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/OyadotAI/oya-browser
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/oya-browser

## What it does

Oya Browser connects over one remote MCP endpoint, `https://oyabrowser.com/mcp/pool`, and authenticates with your Oya API key. If you self-host, swap in the address of your own deployment.

The agent gets browser control: navigate to a page, read its text with numbered elements, click and type. Agent activity stays in its own tabs. A run that worked can become a playbook, replayable with new inputs, and the generated Playwright module sits next to it for inspection.

The key is not optional. Without an `Authorization: Bearer $OYA_API_KEY` header the endpoint refuses the request, so create the key at oyabrowser.com first. The desktop app pairs with Claude, Codex, Cursor and VS Code, and a person can switch between AI Mode and Human Mode mid-task. You can also drive the browser from Node.js 20 or newer with the SDK, pointing it at Oya Cloud, your deployment, or another provider while keeping the same calls.

## Requirements
- Remote server: `https://oyabrowser.com/mcp/pool`
- Works with: Playwright, Chrome

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http oya-browser https://oyabrowser.com/mcp/pool
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add oya-browser --url https://oyabrowser.com/mcp/pool
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "oya-browser": {
            "url": "https://oyabrowser.com/mcp/pool"
        }
    }
}
```

### GitHub Copilot

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

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http oya-browser https://oyabrowser.com/mcp/pool
```

## When to use it
- Walk through a multi-step portal form and read back the result
- Fetch a page as numbered markdown the agent can act on
- Record a successful run into a playbook and replay it with new inputs
- Keep agent tabs separate from the ones you use by hand

## Example prompts
- Connect Oya Browser, open `https://news.ycombinator.com` and summarize the top stories
- Go through the signup flow in Oya and fill the form from `data.json`
- Replay the authorization playbook with new inputs and show me the generated Playwright module

## Similar
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89433
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [AIHawk](https://affpapa.org/en/nevibecode/mcp/aihawk.md) — MCP server · ★ 32221
- [Skyvern](https://affpapa.org/en/nevibecode/mcp/skyvern.md) — MCP server · ★ 23263
- [SeleniumBase MCP](https://affpapa.org/en/nevibecode/mcp/seleniumbase-mcp.md) — MCP server · ★ 13169
- [apify-mcp-server](https://affpapa.org/en/nevibecode/mcp/apify-mcp-server.md) — MCP server · ★ 12927

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md