Browser Forest

com.browserforestPublished by browserforest.comOfficial publisherv1.0.0Updated Oct 24, 2026

Undetectable cloud browser sessions for AI agents and scrapers. Navigate, extract, click, captcha.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant cloud browser sessions to navigate pages, extract content, click, and handle captchas.

What you can do
Browser Forest provides cloud browser sessions for AI agents and scrapers, described as undetectable. Through the remote endpoint an assistant can navigate pages, extract content, click elements, and deal with captchas. The manifest lists no individual tools, so the exact tool set is not documented here.
When to use it
Consider it when an assistant needs to drive a hosted browser for web navigation, content extraction, or clicking through pages, including sites that block ordinary automated browsers. It is less relevant if you only need static page fetching or already run your own browser automation locally.
Requirements
A remote streamable HTTP endpoint at browserforest.com; no local package or runtime is needed. Authentication is OAuth and is required, so an account with the provider is implied. Network access to the endpoint is required.
Before you install
Sessions run in the provider's cloud, so pages visited and data extracted pass through a third party. The service is positioned around evading bot detection, which may conflict with site terms of service or applicable rules. OAuth grants the provider access tied to your account; review the scopes before authorizing.

Installation

In SourceWeft

  1. Open Browser Forest in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.browserforest%2Fbrowser-forest/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "browser-forest": {
      "type": "http",
      "url": "https://browserforest.com/api/mcp/bf"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.