mcpField
C
CloudBrowser

CloudBrowser

Remote
cloudbrowser.aiBrowser Automation0Updated 2d ago
RepositoryVisit website

About CloudBrowser

CloudBrowser is a hosted Chrome browser service for AI agents and assistants that need to interact with web pages. It supports page actions and saved sessions, while allowing a person to watch or take over the browser remotely.

Key features

  1. 01Open and connect to cloud Chrome browsers
  2. 02Navigate, read pages, click and type
  3. 03Find elements and run scripts
  4. 04Capture screenshots and detect CAPTCHAs
  5. 05Save and resume browser sessions
  6. 06Watch or take over through remote desktop

Use cases

  1. 01Automate navigation and interaction with web pages
  2. 02Inspect page content and capture screenshots
  3. 03Resume a saved browser session
  4. 04Monitor or manually take over a browser

MCP support

The hosted Streamable HTTP MCP server exposes browser lifecycle, page interaction, session, screenshot and remote desktop tools. Clients authenticate using OAuth.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.cloudbrowser.ai
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

CloudBrowser MCP Server

Give ChatGPT, Claude and your AI agents a real browser. CloudBrowser runs Chrome in the cloud. Your assistant opens a browser, navigates, reads pages, clicks, types and takes screenshots, and you can watch live or take over at any time.

  • Endpoint: https://mcp.cloudbrowser.ai (Streamable HTTP)
  • Auth: OAuth, sign in with your CloudBrowser account
  • Website: https://cloudbrowser.ai/mcp
  • Official MCP Registry: ai.cloudbrowser/mcp

What you can do

  • Open cloud Chrome browsers in your CloudBrowser account and connect to them.
  • Navigate, read page content, find elements, click, type, run scripts and take screenshots.
  • Save browser sessions and resume them later.
  • Start a remote desktop to watch the browser live or take over.
  • Detect CAPTCHAs. Login and verification walls stay with you.

Connect

The server uses OAuth. Your client opens a browser window, you sign in with your CloudBrowser account and approve access. You do not copy an API key.

Claude (claude.ai and Claude Desktop)

Open Settings → Connectors → Add custom connector, enter https://mcp.cloudbrowser.ai and select Connect.

Claude Code
claude mcp add --transport http cloudbrowser https://mcp.cloudbrowser.ai

Then run /mcp in Claude Code and authenticate cloudbrowser.

Codex CLI
codex mcp add cloudbrowser --url https://mcp.cloudbrowser.ai
codex mcp login cloudbrowser
Cursor

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "cloudbrowser": { "url": "https://mcp.cloudbrowser.ai" }
  }
}
VS Code
code --add-mcp '{"name":"cloudbrowser","type":"http","url":"https://mcp.cloudbrowser.ai"}'
Gemini CLI
gemini mcp add --transport http cloudbrowser https://mcp.cloudbrowser.ai
ChatGPT and other clients

Add a custom connector (in ChatGPT, developer mode) with the URL https://mcp.cloudbrowser.ai. Any client that supports Streamable HTTP and MCP OAuth works.

Tools

The server advertises 20 tools. Your client gets the current schemas from tools/list.

  • Workspace: browser_workspace, resume_saved_session
  • Browser lifecycle: open_browser, close_browser, get_browsers, start_remote_desktop, stop_remote_desktop
  • Saved sessions: get_saved_sessions, remove_saved_session
  • Connections: connect_to_browser, disconnect_browser, get_connected_browsers
  • Page work: navigate_to_url, get_page_content, click_element, type_text, get_elements, take_screenshot, evaluate_script, detect_captcha

Authentication and account

OAuth 2.1 with PKCE and dynamic client registration. Sign in with your CloudBrowser account. Scope: browser:control (openid email optional). Developers can send their own account token instead: Authorization: Bearer <your CloudBrowser API token>. Keep the token in your client's secret settings, never in a prompt.

You need a CloudBrowser account. Browser usage follows your CloudBrowser plan.

Links

About this repository

This repository is the public home of the hosted CloudBrowser MCP server. It holds this setup guide and the registry metadata (server.json for the official MCP Registry, glama.json for Glama). The server runs as a hosted service at https://mcp.cloudbrowser.ai. Its source code is not in this repository.

Found a problem or have a question? Open an issue.

License

The contents of this repository are available under the MIT License.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.