Browser tools
MCP
Browserbase
Give an agent a browser session.
Free tier
SOURCE-BACKED AGENT TOOLS
Find a browser tool that fits your agent.
Browser automation can involve remote browser sessions, navigation, screenshots or interactive actions. A service may document only some of these capabilities. Start with the published candidates below and review the precise action, transport and access requirements before connecting a browser to an agent.
COMPARE THE PUBLISHED OPTIONS
How we review sources →5 catalogue listings
Alphabetical order. These are published metadata records, not a performance ranking. Pricing, connection requirements and evidence status remain visible on each profile.
Browser tools
MCPREST
Browserless
Control a browser from an agent.
Free tier
Browser tools
MCP
Oya Browser
Control browser sessions through an API-key-authenticated MCP endpoint.
Free tier
Browser tools
MCP
Screen Browser
Create narrated web-app walkthrough videos through MCP.
Subscription
Browser tools
RESTx402
Steel x402
Scrape, screenshot or render pages using wallet payments.
Usage-based
What to check before connecting
Confirm the session model
Check whether the operation runs in a remote session or a local browser, whether sessions persist, and where any credentials or downloaded data will live. A hosted website is not itself proof of a remote browser API.
Verify the required action
Read the provider documentation for screenshots, navigation, form interaction or other actions your task requires. Do not infer a capability from the word browser alone.
Control actions and spending
Review the host’s approval model before allowing submissions, purchases or account changes. Catalogue discovery grants no permission for a later consequential browser action.
Questions to resolve before integration
Can a browser agent use a provider without an account?
Check the exact listing and provider connection guide. Some operations require a provider key or host-managed login. ToolSkipper does not inspect or create those connections when you browse a listing.
Does browser support mean screenshot support?
No. Screenshot capture must be documented for the particular endpoint or tool. A general browser description or evidence from a different transport is insufficient.
Inspect the evidence, then choose.
Read source links and check dates before relying on a service. ToolSkipper discovery never connects accounts or authorizes a payment.
Connect your agent →