Baizhi Cloud Browser (CapyBrowser)

io.github.ctcbyzxPublished by GitHub account ctcbyzxv0.1.16-metadata.1Updated Oct 25, 2026

Baizhi Cloud Browser (CapyBrowser): cloud sessions via MCP; page actions use a CDP client.

VerifiedStreamable HTTPWeb executableBrowser Automation

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant cloud browser sessions, driving page actions through a CDP client.

What you can do
Open and manage cloud browser sessions through the remote MCP endpoint. Perform page actions in those sessions via a CDP client, such as navigating and interacting with page content. No individual tools are documented in the supplied listing, so exact capabilities should be confirmed against the provider's documentation.
When to use it
Useful when an assistant needs to act on web pages in a hosted browser session rather than on the user's own machine, for example for page interaction tasks that should run in the cloud.
Requirements
A remote MCP connection to the provider's endpoint over streamable HTTP. A bearer token supplied in the Authorization header is required.
Before you install
The Authorization header carries a secret bearer token; keep it private and scope it as narrowly as the provider allows. Page actions in a cloud session may submit forms, click controls or otherwise change state on third-party sites, and page content is handled by the remote provider.

Installation

In SourceWeft

  1. Open Baizhi Cloud Browser (CapyBrowser) in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.ctcbyzx%2Fbaizhi-cloud-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.

{
  "mcpServers": {
    "baizhi-cloud-browser-capybrowser": {
      "type": "http",
      "url": "https://capybrowser.app.baizhi.cloud/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

2
  1. v0.1.16-metadata.1LatestOct 25, 2026
  2. v0.1.15Oct 21, 2026

Score

67% 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.

  • 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.