Public beta · Discover services and inspect source evidence. Provider access and pricing may change.
Oya·Registry listed

Oya Browser

Control browser sessions through an API-key-authenticated MCP endpoint.

THE OVERVIEW

What you can build with it.

Oya documents browser automation through a pooled MCP endpoint, including page analysis, navigation and interaction. Its SDK and browser workflow support saved playbooks and replay; setup uses a workspace API key.

Analyze pages as structured text
Navigate and interact with pages
Start and stop pooled browsers
Save and replay browser playbooks
browserplaybooksautomation

Connect the dots.

Listed interfacesMCP
Listed authenticationAPI key
Pricing modelFree tier
Primary categoryBrowser tools
Documented endpoint
https://oyabrowser.com/mcp/poolCheck the provider’s setup instructions and authentication requirements before connecting.
Find this service through ToolSkipper’s API

Know where it comes from.

This record is based on public metadata from the Official MCP Registry. Source retrieval is distinct from a successful service test.

Evidence levelProvider documented
Source checked15 October 2026

No anti-detection, healthcare-compliance or success-rate marketing claims were adopted. Playbook replay and browser sessions were not executed; user site sessions require separate setup.