Remote Browser MCP Server from MCPBundles

com.mcpbundlesPublished by mcpbundles.comOfficial publisherv1.0.0Updated Oct 24, 2026

Automate cloud Chrome—navigate, click, type, screenshot, run code, record screen video

The publisher's own server: Agent Interviews MCP Server from MCPBundles

VerifiedStreamable HTTPWeb executableBrowser Automation

Server details

Identifier: com.mcpbundles/remote-browser
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to mcpbundles.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.mcpbundles%2Fremote-browser.svg)](https://sourceweft.com/mcp/com.mcpbundles%2Fremote-browser?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant drive a cloud-hosted Chrome browser to navigate pages, click, type, take screenshots, run code and record video.

What you can do: This remote server gives an assistant control of a Chrome browser running in the cloud. According to the description, it can navigate to pages, click, type text, capture screenshots, execute code and record screen video. It is reached over streamable HTTP at a hosted endpoint rather than installed locally.
When to use it: Useful when an assistant needs to interact with web pages that require a real browser, such as filling forms, checking rendered content, capturing screenshots or recording a browsing session, without running a browser on the user's own machine.
Requirements: A remote MCP endpoint over streamable HTTP. Authentication is required via the Authorization header, using either an OAuth2 Bearer token or an API key. Network access to the hosted endpoint is needed.

Before you install

The Authorization header carries a secret credential (OAuth2 token or API key) that grants access to the hosted browser service. The assistant can click and type on live web pages and run code, which may submit forms, change data or trigger actions on third-party sites. Screenshots and video recordings may capture sensitive page content.

Installation

In SourceWeft

Open Remote Browser MCP Server from MCPBundles in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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.mcpbundles%2Fremote-browser/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": {
    "remote-browser-from-mcpbundles": {
      "type": "http",
      "url": "https://mcp.mcpbundles.com/bundle/remote-browser/"
    }
  }
}

README

This repository has no README.

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestSep 16, 2026

Score

60% 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
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.