Oya Browser MCP Server

Everyone else drives Chrome from the outside. We built the browser. The automation lives inside it, not attached over the debugging protocol, so your agents stop. It is available as a remote MCP endpoint.

Teams that work with browser automation, cdp and headless chrome and want a hosted endpoint instead of running a local process. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-09-29 · ★ 338 · #128 OF 290 MAINTAINED BROWSER AUTOMATION · VERIFIED 2026-09-30

NOASSERTION · TypeScript servers · how we verify → /methodology

01 · Install Oya Browser

Claude Code

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

Claude Desktop / Cursor / VS Code - add to config

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

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

https://oyabrowser.com/mcp/pool

transport: streamable-http

endpoint alive - authentication required · probed 2026-09-30

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as remote - your agent's requests go to oyabrowser.com

endpoint auth requires authentication - rejected our unauthenticated MCP initialize

license no standard license detected - usage rights unclear; check the repo before commercial use

registry namespace io.github.OyadotAI is GitHub-verified and matches the repo owner

03 · What Oya Browser can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v1.0.142 · 2026-09-29

Changed · Maintenance and fixes. · All release notes:

v1.0.141 · 2026-09-29

Changed · Maintenance and fixes. · All release notes:

v1.0.140 · 2026-09-29

Changed · Maintenance and fixes. · All release notes:

04 · Who maintains Oya Browser

Oya Browser is maintained by oyadotai. It's the only MCP server we track from this author; the repo dates to Mar 2026.

05 · Facts

category
browser automation - ranked #128 of 290 actively-maintained browser automation servers as of 2026-09-30.
release cadence
10+ releases in the last 90 days (latest 2026-09-29)
registry
io.github.OyadotAI/oya-browser (active, first published 2026-09-11 · 73 versions)

06 · Oya Browser FAQ

What is Oya Browser?

Everyone else drives Chrome from the outside. We built the browser. The automation lives inside it, not attached over the debugging protocol, so your agents stop. It is available as a remote MCP endpoint.

Is Oya Browser still maintained?

Yes - as of 2026-09-30, its last commit was 2026-09-29 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install Oya Browser?

Run `claude mcp add oyadotai-oya-browser --transport http https://oyabrowser.com/mcp/pool`. You can also paste the ready-made client config above.

Does Oya Browser require authentication?

Yes - when we probed the endpoint on 2026-09-30, it rejected an unauthenticated MCP initialize; you'll need credentials to connect.

07 · Alternatives to Oya Browser

More browser automation MCP servers · Notebooklm MCP Secure · Digitaltableteur · Vigilis · Playrunner · Browserbash

More TypeScript MCP servers · GitLab Docs · DJ Claude · Symbols · Kaiord · Packmindhub MCP Server · see all