Oya Browser

Name: Oya Browser
Author: OyadotAI

by OyadotAIversion 1.0.210i★ 349iRuns in the cloud

Registry nameio.github.OyadotAI/oya-browser

Overview

Description from the maker (original English)

Real Chrome for agents: start a browser, read pages as numbered markdown, click, type, hand off.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi4 of 5 passedChecked from public information; code not scanned yet
UsageiEarly★ 349

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Web & browsers
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

You need

Runs in the cloudNothing to install; it connects over the internet

Claude DesktopClaude CodeCursorVS Code

Open Claude Desktop → Settings → Connectors → Add custom connector, and paste this address

https://oyabrowser.com/mcp/pool

Run this in your terminal

claude mcp add --transport http oya-browser https://oyabrowser.com/mcp/pool --header 'Authorization: Bearer {api_key}'

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "oya-browser": {
      "url": "https://oyabrowser.com/mcp/pool",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "oya-browser": {
      "type": "http",
      "url": "https://oyabrowser.com/mcp/pool",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Values you fill in

Authorization secret required HTTP header
Your Oya API key from oyabrowser.com, sent as a bearer token

Values marked secret are keys to your account. Never share them or paste them into a chat.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 5, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account OyadotAI, which owns the repo
✓ Pass
Still maintained
Code last changed yesterday
! Caution
Has a licence
GitHub could not identify the licence type; open the file to check
✓ Pass
Endpoint responds
Responded in 980 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Needs the server’s tool list first; this check starts in the next step

Compared with others in Web & browsersi

More stars than 11% of the other 9 servers in this category
Published to the registry more recently than 89% of the other 9 servers in this category
Basic checks equal to or better than 0% of the other 9 servers in this category

Compared only with servers in this prototype, not the whole registry.

Common questions

Is Oya Browser safe?

It passed 4 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (1.0.210) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 15 days ago

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 14 days ago

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

The browser for regulated industries (community version).

People and AI agents work together in one browser, with control over where it runs and how it is governed.

Download Oya Browser · Get started in the cloud · Self-host Oya · For enterprise, contact sales@getoya.ai

A run in the Oya desktop app, sped up. The portal and patient data are fictional. Watch run 1 · run 2 · run 3 .

This repository contains the Oya Browser community edition. People and AI agents work together in one browser: agents can use an existing signed-in browser, start managed cloud browsers, or connect through familiar tools and APIs. People can watch the work, step in when needed, and keep control of browser access and repeatable tasks.

The enterprise edition, including the HIPAA-ready offering, is maintained in a separate private repository. Contact sales@getoya.ai to learn about that edition.

Choose how to get started

Use Oya with an AI assistant

Install the desktop app, sign in, and connect your assistant from the app. Oya works with Claude Code, Codex, Cursor and VS Code. People can see the agent's browser activity and take control when a task needs their attention.

Download the desktop app · Agent setup guide

Control a browser from Node.js

Install the SDK and create an API key at oyabrowser.com. Node.js 20 or newer is required.

npm install @oya-ai/browser

Set OYA_API_KEY, then run:

import { Oya } from '@oya-ai/browser';

const oya = new Oya(); const browser = await oya.browser.start();

try { await browser.goto('https://news.ycombinator.com'); console.log(await browser.ask('Summarize the top three stories.')); } finally { await browser.stop(); }

With no browser provider configured, start() can use the Oya desktop browser already connected to your account. To start cloud or self-hosted browsers, configure a provider with npx @oya-ai/cli init. The SDK and CLI can also use Browserbase, Steel, Anchor, Browser Use, or a browser you provide. Your application can keep the same SDK calls when you change providers.

SDK guide · Runnable examples · CLI guide

Connect over MCP

For assistants that support remote MCP, connect to https://oyabrowser.com/mcp/pool and authenticate with your Oya API key. For Claude Code:

claude mcp add --transport http oya https://oyabrowser.com/mcp/pool \

--header "Authorization: Bearer $OYA_API_KEY"

Use the same endpoint with your self-hosted server URL when you run your own deployment.

Agent instructions and MCP reference

For AI agents

Use the agent reference for setup instructions, available tools, SDK examples, and MCP configuration. The desktop app can pair with Claude Code, Codex, Cursor, and VS Code. For remote MCP clients, connect to https://oyabrowser.com/mcp/pool with your Oya API key.

Run Oya in your own environment

Use the installer to set up a self-hosted instance:

curl -fsSL https://raw.githubusercontent.com/OyadotAI/oya-browser/main/install.sh | sh

For production, choose Docker, Amazon ECS, Kubernetes, or GKE. The deployment guides cover configuration, storage, upgrades, and operations.

Self-hosting guide · Deployment templates

What you can do with Oya

Work in a signed-in browser. Connect the desktop app and reuse logins imported from Chrome, Arc, Brave, Edge, or Firefox. Set up logins.
Keep a person in control. Watch an agent work, switch between AI Mode and Human Mode, and keep agent activity in its own tabs.
Turn a successful run into a playbook. Replay repeatable tasks with new inputs, inspect the generated Playwright module, and export or import workflows. Playbook details · Replay benchmark.
Choose where browsers run. Use Oya Cloud, your own deployment, supported browser providers, or a browser you provide. Why route through Oya?.
Operate with governance controls. Self-hosted community deployments include host egress rules and a tamper-evident audit trail. See the control evidence and trust center.

For contributors

Oya is made up of the browser, control plane, console, SDK, and CLI. Start with the architecture map, then read the guide for the part you plan to change.

Development

Requirements and commands vary by project area. See Working in this repository for the conventions and complete command list. To install dependencies across the workspace:

npm run setup

Common checks:

npm run lint

npm run format:check npm test

The full test command builds the SDK and runs the server, CLI, package, and script suites. For changes in the UI or browser app, run the checks listed in that part's package.json and architecture guide as well.

Packages and project areas

Path	What it contains
`packages/sdk`	`@oya-ai/browser`, the TypeScript SDK (MIT)
`packages/cli`	`@oya-ai/cli`, setup and command-line tools (MIT)
`browser`	Oya's desktop browser and cloud browser image
`server`	API, browser connections, MCP, and control plane
`ui`	Web console and public site
`examples`	SDK and browser integration examples
`docs`	Operator guides and product details

License

The SDK and CLI are MIT licensed. The rest of the project is available under the Sustainable Use License. See LICENSE.md for permitted use, self-hosting terms, and commercial licensing details.