What you can do with Remote Browser

Built for

Demo & Marketing Video, Browser Automation, Web QA, Public-Site Testing, Agent Workflows

Example workflows

Record a site tour video

Records a multi-page screencast from the cloud browser for a demo video.

Try this

Start a screen recording, walk through the homepage, pricing, and blog pages while scrolling each, then stop and give me the video.

Review a public landing page

Uses a zero-install cloud browser for page review.

Try this

Open this public URL in the remote browser, capture a screenshot, summarize the first fold, and list visible conversion issues.

Test an interactive flow

Turns cloud browser automation into product QA.

Try this

Navigate through this product flow, click the primary calls to action, and report where the browser gets blocked.

Research a competitor page

Combines browsing and visual inspection for research.

Try this

Load the page, read visible text, take a screenshot, and summarize the main claims and navigation options.

Context to know first

What is Remote Browser best for?

It is best for zero-install browser automation against public websites when you do not want Chrome running on your machine.

How is Remote Browser different from Local Browser?

Remote Browser runs Chrome in MCPBundles cloud. Local Browser runs on your machine through Desktop and reaches localhost directly.

Can it capture screenshots?

Yes. The remote browser can take screenshots and return visual content for agents to inspect during page review and QA workflows.

AI Skill
SKILL.md

Domain knowledge for Remote Browser — workflow patterns, data models, and gotchas for your AI agent.

Remote Browser (Playwright MCP)

Playwright MCP server — cloud-hosted Chrome with no local install. Same Playwright browser automation tools as Local Browser but Chrome runs in the cloud.

When to Use

  • Browser automation without installing Chrome or Playwright locally
  • Testing against public URLs with zero setup
  • Recording a screen video or capturing stills of a live site tour from the cloud, with no screen-capture software on the user's machine
  • When the user wants a cloud browser instead of running one on their machine

Screen Recording & Video Capture

Capture is not the video file. Stop recording uploads JPEG frames to S3 and returns asset_id. That alone does not satisfy “give me the video” — you must export and return presigned MP4 URLs.

The cloud browser records server-side over the live session:

  • Start a screen recording, then navigate and scroll while capturing; stop to flush frames. Recording survives navigation and scrolling within one take.
  • Or record a short fixed-length clip of the current page in a single step.
  • Capture directed keyframes (“beats”) for curated walkthroughs (Marketing Studio cinematic presets).
  • After stop, poll browser_get_recording_status until status is ready (never treat flushing as done).
Deliver an MP4 when the user asks for “the video”

Use the same Remote Browser bundle — no separate Marketing Studio enablement required:

  1. browser_get_recording_status with the stop-recording asset_id until status is ready.
  2. browser_submit_screencast_export with that asset_id and preset=hero_from_capture (or product_hunt_kit for a launch kit).
  3. browser_get_screencast_export_status with the returned job_id until status is completed.
  4. Give the user the presigned_url values from outputs (typically hero.mp4). Do not stop at asset_id, frame counts, or “use Marketing Studio” unless export tools are unavailable.

Optional: Marketing Studio bundle adds timeline editing, MCP App preview, and extra presets (cinematic, mixed, device_mockup). Remote Browser screencast export covers the common “record a tour → MP4 link” path.

This works on cloud (Remote Browser) and local (Local Browser) capture; export runs async on the server (poll — never wait inside one tool call for ffmpeg to finish).

Localhost Access

For public URLs, no extra setup is needed. For localhost dev servers, the cloud browser needs a tunnel:

  1. User runs: pip install mcpbundles && mcpbundles login && mcpbundles proxy start
  2. User runs: mcpbundles proxy expose <port> (e.g. mcpbundles proxy expose 3000)
  3. Pass http://localhost:<port> to **Browser navigate** — the tool automatically rewrites it to the public tunnel URL
  4. The cloud browser navigates through the tunnel to the user's local machine

Key Details

  • Zero setup for public URLs — just enable the bundle and go
  • Localhost requires mcpbundles proxy expose <port> first
  • One tab only — multi-tab not supported
  • Use wait_until="domcontentloaded" for slow pages and SPAs (default on cloud navigate)
  • For recordings, poll until capture is ready, then run screencast export and poll until completed before telling the user the video is done

Interaction workflow (required)

Every click, type, hover, or drag must use refs from a fresh page snapshot — never invent CSS selectors.

  1. Navigate — open the URL with wait_until=domcontentloaded on SPAs; use timeout=30000 when pages are slow.
  2. Snapshot — capture the accessibility tree for the current page. Each node has opaque ref (e1, e2, …) and name.
  3. Interact — pass both ref (e.g. e12) and element (the node's name) to the click, type, or hover tool.
  4. Re-snapshot after navigation — page changes invalidate old refs; snapshot again before the next click.
  5. Stuck loading UI — if a wait-for condition times out, snapshot the page and choose a different path (do not set max_seconds above 60 without user request).
  6. Batch form fills — use the multi-field form fill tool when CSS selectors are appropriate; single-element tools reject invented selectors.
  7. Recordings — stop returns asset_id; poll until ready; when the user wanted a video file, submit screencast export and poll until completed, then share presigned MP4 URLs from outputs.

Tools in this Server (40)

Browser Click

Click a web page element. Capture a page snapshot first, then copy opaque ref (e.g. e12) and element from the target node → click. Unknown or invented...

Browser Close

Close the current page or the entire browser session. Use to release resources when done with browser automation.

Browser Console Messages

Returns console messages. Note: Only messages logged AFTER browser session started are available.

Browser Drag

Perform drag and drop between two elements

Browser Emulate

Emulate network conditions and CPU throttling to test performance on slow connections or devices

Browser Evaluate

Evaluate JavaScript expression on page or element

Browser File Upload

Upload files to a file input or upload button using base64-encoded file payloads.

Browser Fill Form

Fill multiple form fields. Each field ref can be an opaque handle from the latest page snapshot (e.g. e12) or a CSS selector.

Browser Get Console Message

Get detailed information about a captured console message including structured arguments, stack trace, and source location.

Browser Get Cookies

Get browser cookies including HttpOnly cookies. Returns name, value, domain, path, expires, httpOnly, secure, and sameSite for each cookie. Useful for...

Browser Get Network Request

Get detailed information about a captured network request: status, response headers, timing, and a truncated text body when available.

Browser Get Recording Status

Poll a browser capture asset until S3 flush completes. When status is ready, call browser_submit_screencast_export, then poll browser_get_screencast_e...

Browser Get Screencast Export Status

Poll a screencast export job. When status is completed, outputs include presigned MP4 download URLs — give those links to the user.

Browser Get Storage

Read localStorage or sessionStorage from the current page. Returns all key-value pairs or a specific key. Useful for extracting auth tokens, user pref...

Browser Get Visible Text

Get the visible text content of the current page. Lighter than a full accessibility snapshot when you only need text. Hidden elements (display:none, v...

Browser Handle Dialog

Handle a dialog

Browser Hover

Hover over a web page element. Capture a page snapshot first, then copy opaque ref (e.g. e12) and element from the target node → hover.

Browser Iframe Click

Click an element inside an iframe. Capture a page snapshot to get iframeRef and element ref.

Browser Iframe Fill

Fill an input field inside an iframe. Capture a page snapshot to get iframeRef and field ref.

Browser Navigate

Navigate to a URL in the browser. Returns final URL (after redirects), page title, and HTTP status. For cloud-hosted sessions and SPAs, prefer wait_un...

Browser Navigate Back

Go back to the previous page

Browser Network Requests

Returns network requests for the current page with request IDs for detailed inspection

Browser Performance Trace

Start or stop performance tracing to analyze page performance, Core Web Vitals (LCP, FID, CLS), and identify bottlenecks

Browser Press Key

Press a key or key combination on the keyboard. Supports special keys (Enter, Escape, Tab) and modifiers (Control, Shift, Alt, Meta). Optionally focus...

Browser Record Clip

Record a short screencast on the current browser tab via CDP (Local or Remote Browser; start → wait → stop in one call). Returns asset_id; poll record...

Browser Resize

Resize the browser window

Browser Run Code

Run a Playwright Python code snippet. The code receives 'page' (Playwright Page object) and can perform any page interaction. Use 'return' to return a...

Browser Save As PDF

Save the current page as a PDF file. Returns base64-encoded PDF if path not provided.

Browser Scroll

Scroll the page by direction/amount, scroll to top/bottom, or scroll a specific element into view. Essential for lazy-loading pages and content below ...

Browser Select Option

Select an option in a dropdown

Browser Set Cookies

Set or delete browser cookies including HttpOnly cookies. Use 'cookies' to add/update cookies (name+value required, domain defaults to current page). ...

Browser Snap Beat

Capture one crisp keyframe of the current page as a film beat, with an optional caption. Call once per scene (navigate/scroll, then snap). Finish by s...

Browser Snapshot

Capture accessibility snapshot of the current page. Nodes include opaque refs (e1, e2, …). Set interactive_only=true for a compact flat index of click...

Browser Start Recording

Start screen recording on the active browser tab via CDP screencast (Local Browser or Remote Browser). Navigate and interact, then stop recording to u...

Browser Stop Recording

Stop the active browser screencast and enqueue upload of JPEG frames to S3. Returns asset_id immediately; poll recording status until ready.

Browser Submit Screencast Export

Turn a ready browser screencast capture into an async MP4 export. Returns job_id immediately; poll browser_get_screencast_export_status until complete...

Browser Tabs

List, create, close, or select a browser tab.

Browser Take Screenshot

Take a screenshot of the current page. You can't perform actions based on the screenshot; capture an accessibility snapshot for element interactions.

Browser Type

Type text into an editable element. Capture a page snapshot first, then copy opaque ref (e.g. e12) and element from the target field → type.

Browser Wait For

Wait for a page condition: visible/hidden text, CSS selector(s), a polled JavaScript ready check, a streaming probe ({streaming, measure}), or a fixed...

Frequently Asked Questions

What is Remote Browser best for?

It is best for zero-install browser automation against public websites when you do not want Chrome running on your machine.

How is Remote Browser different from Local Browser?

Remote Browser runs Chrome in MCPBundles cloud. Local Browser runs on your machine through Desktop and reaches localhost directly.

Can it capture screenshots?

Yes. The remote browser can take screenshots and return visual content for agents to inspect during page review and QA workflows.

Can it record a screen video?

Yes. The cloud browser records a screencast while it navigates and scrolls. After recording, MCPBundles exports an MP4 on the server and returns presigned download links — you do not need separate screen-recording software on your machine.

When does localhost require extra setup?

Because the browser runs in the cloud, localhost URLs need to be exposed through MCPBundles Desktop before the remote browser can reach them.

How do I connect Remote Browser to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/remote-browser. Authentication is handled automatically.

How many tools does Remote Browser provide?

Remote Browser provides 40 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does Remote Browser require?

Remote Browser uses open data APIs — no authentication required.

Setup Instructions

Connect Remote Browser to any MCP client in minutes

MCP URL
https://mcp.mcpbundles.com/bundle/remote-browser

One-click install:

The link prefills the Add custom connector dialog — you still review the values and click Add, then Connect to complete OAuth.

Or add manually

  1. Open claude.ai → Settings → Connectors.
  2. Click the + button and choose Add custom connector.
  3. Set Name to Remote Browser and paste the MCP URL into Remote MCP server URL.
  4. Click Add. Remote Browser will appear under Not connected — select it and click Connect to complete OAuth.
Name: Remote Browser
Remote MCP server URL: https://mcp.mcpbundles.com/bundle/remote-browser
Authentication: OAuth

Custom connectors at claude.ai require a paid Claude plan (Pro, Max, Team, or Enterprise).

Try Remote Browser now

No API key or third-party login required. Chat with AI and run tools instantly.

Remote Browser MCP Server & Skill