Add to your AI client, then sign in once when you connect.
Control Chrome on your machine from Claude Code or Cursor — reach localhost dev servers, capture screenshots, and walk through flows without a cloud browser.
This listing identifies a third-party integration. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Live probe refreshed Nov 3, 2026 · Endpoint host mcp.mcpbundles.com
Built for
Frontend Developers, QA Engineers, Localhost Debugging, Product Operations
Connect Local Browser to any MCP client in minutes
https://mcp.mcpbundles.com/bundle/browserThis server may ask you to sign in when your AI client connects.
Prefer the browser? Open in MCPBundles Studio
Sign in to connect your credentials and start running tools from the chat.
Connect to your AI clientMCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
https://mcp.mcpbundles.com/bundle/browserThis server may ask you to sign in when your AI client connects.
Prefer the browser? Open in MCPBundles Studio
Choose your AI client below. When you connect, sign in to MCPBundles once — we store your service credentials for every client.
Browse all toolsSmoke-test localhost
Uses direct localhost access that cloud browsers cannot reach.
Open http://localhost:3000, wait for the dashboard to render, and report any console errors or broken layout.
Walk a signup flow
Combines snapshots, clicks, typing, and visible text review.
Navigate through the signup form on localhost, fill fields with test data, and flag validation or layout issues before submitting.
Capture visual evidence
Uses screenshots for visual QA and page review.
Load the dashboard, take a screenshot, and describe what is visible above the fold on desktop width.
Debug a slow page
Turns browser diagnostics into actionable frontend notes.
Open this page, capture network requests and console messages, then summarize what is blocking first paint.
What is Local Browser best for?
It is best when your agent needs to drive Chrome on the same machine as your code — localhost dev servers, internal apps, and interactive UI debugging without exposing anything to the public internet.
How does Local Browser differ from Remote Browser?
Local Browser runs Chrome on your machine through MCPBundles Desktop, so it reaches localhost directly. Remote Browser runs Chrome in the cloud and needs a tunnel for localhost.
Do I need MCPBundles Desktop?
Yes. Desktop supervises the secure tunnel between your agent and local Chrome. Install it on the Mac or PC where Chrome runs and keep it open while you automate.
Domain knowledge for Local Browser — workflow patterns, data models, and gotchas for your AI agent.
Chrome runs on the user's machine and is controlled through the MCPBundles Desktop proxy CDP tunnel. The browser resolves localhost on that same machine — ideal for dev-server QA, interactive debugging, and visual verification.
Cinematic tour (recommended):
Raw screencast: start recording → navigate → wait while still recording → stop recording → browser_wait_for_recording → export hero_from_capture or product_hunt_kit → browser_wait_for_screencast_export for presigned MP4 URLs.
Mixed tour (Ken Burns + screencast): run a YAML journey from product/browser/journeys/studio-mixed-tour.yaml (pass full document as journey_yaml + workspace) — snap beats, flush beats, record Studio autosend, flush screencast. Link both asset ids on the project (beat_capture_id, screencast_capture_id), then Marketing Studio export with preset=mixed or device_mockup.
Chat stream screencast: start recording → navigate → wait with js_probe (returns {streaming, measure} until streaming stops and measure grows) → stop recording. Or selector_gone / selectors_gone for spinners. time is in seconds. Example YAML: product/browser/journeys/chat-autosend-screencast.yaml — pass contents as journey_yaml; uses checked-in probe_preset for Studio QA only.
Open a page — resize viewport, then navigate. Success means the navigate response includes URL, title, and HTTP 200.
Sign in then continue — navigate to the app's login URL with callbackUrl set to the post-auth destination. Prefer batch form fill with CSS selector refs, or click/type each field with snapshot refs. Redirects can take 1–3 seconds; re-read location from JavaScript evaluation or from the snapshot's URL field.
Review UI quality — after navigate: run the combined UX review for a structured report with clustered ui_findings, optional visual_findings, and a limits block (layout, accessibility, console, form, copy). Set visualCritique=true for PydanticAI vision observations; use captureFrames (desktop, mobile, desktop_scroll_end, mobile_menu_open) for richer shots. Or run responsive capture, accessibility audit, and layout probe individually. Use snapshot with boxes=true or screenshots when you need pixels.
Showing 53 of 53
Showing 53 of 53 tools from the public preview. Connect the server to inspect the full live tool list.
Browser Accessibility Audit
browser_accessibility_auditRun an axe-core accessibility audit on the current browser page. Returns structured WCAG violations with selectors and HTML snippets.
Open in Studio[
{
"name": "browser_accessibility_audit",
"title": "Browser Accessibility Audit",
"description": "Run an axe-core accessibility audit on the current browser page. Returns structured WCAG violations with selectors and HTML snippets."
},
{
"name": "browser_call_webmcp_tool",
"title": "Browser Call Webmcp Tool",
"description": "Call a WebMCP tool on the current page by name. Navigate first, list tools, then invoke with JSON input matching the tool schema."
},
{
"name": "browser_click",
"title": "Browser Click",
"description": "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 refs are rejected."
},
{
"name": "browser_close",
"title": "Browser Close",
"description": "Close the current page or the entire browser session. Use to release resources when done with browser automation."
},
{
"name": "browser_console_messages",
"title": "Browser Console Messages",
"description": "Returns console messages. Note: Only messages logged AFTER browser session started are available."
},
{
"name": "browser_drag",
"title": "Browser Drag",
"description": "Perform drag and drop between two elements"
},
{
"name": "browser_emulate",
"title": "Browser Emulate",
"description": "Emulate network conditions and CPU throttling to test performance on slow connections or devices"
},
{
"name": "browser_evaluate",
"title": "Browser Evaluate",
"description": "Evaluate JavaScript expression on page or element"
},
{
"name": "browser_file_upload",
"title": "Browser File Upload",
"description": "Upload files to a file input or upload button using base64-encoded file payloads."
},
{
"name": "browser_fill_form",
"title": "Browser Fill Form",
"description": "Fill multiple form fields. Each field ref can be an opaque handle from the latest page snapshot (e.g. e12) or a CSS selector."
},
{
"name": "browser_find_in_snapshot",
"title": "Browser Find In Snapshot",
"description": "Search the current page accessibility snapshot for nodes by name and return matching refs without dumping the full tree."
},
{
"name": "browser_get_console_message",
"title": "Browser Get Console Message",
"description": "Get detailed information about a captured console message including structured arguments, stack trace, and source location."
},
{
"name": "browser_get_cookies",
"title": "Browser Get Cookies",
"description": "Get browser cookies including HttpOnly cookies. Returns name, value, domain, path, expires, httpOnly, secure, and sameSite for each cookie. Useful for extracting auth tokens (session IDs, API keys) from authenticated browser sessions."
},
{
"name": "browser_get_network_request",
"title": "Browser Get Network Request",
"description": "Get detailed information about a captured network request: status, request/response headers, POST body (when captured), timing, and a truncated text response body when available."
},
{
"name": "browser_get_recording_status",
"title": "Browser Get Recording Status",
"description": "Poll a browser capture asset until S3 flush completes. When status is ready, call browser_submit_screencast_export, then poll browser_get_screencast_export_status for presigned MP4 URLs when the user asked for a video file."
},
{
"name": "browser_get_screencast_export_status",
"title": "Browser Get Screencast Export Status",
"description": "Poll a screencast export job. When status is completed, outputs include presigned MP4 download URLs — give those links to the user."
},
{
"name": "browser_get_storage",
"title": "Browser Get Storage",
"description": "Read localStorage or sessionStorage from the current page. Returns all key-value pairs or a specific key. Useful for extracting auth tokens, user preferences, cached API data, and app state."
},
{
"name": "browser_get_visible_text",
"title": "Browser Get Visible Text",
"description": "Get the visible text content of the current page. Lighter than a full accessibility snapshot when you only need text. Hidden elements (display:none, visibility:hidden) are excluded."
},
{
"name": "browser_handle_dialog",
"title": "Browser Handle Dialog",
"description": "Handle a dialog"
},
{
"name": "browser_hover",
"title": "Browser Hover",
"description": "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."
},
{
"name": "browser_iframe_click",
"title": "Browser Iframe Click",
"description": "Click an element inside an iframe. Capture a page snapshot to get iframeRef and element ref."
},
{
"name": "browser_iframe_fill",
"title": "Browser Iframe Fill",
"description": "Fill an input field inside an iframe. Capture a page snapshot to get iframeRef and field ref."
},
{
"name": "browser_layout_probe",
"title": "Browser Layout Probe",
"description": "Analyze page layout at desktop (1440x900) and mobile (390x844) for horizontal overflow, clipped URLs/slugs in narrow copy rows, narrow readable columns, and tap targets smaller than 44px. Mobile passes scroll main content to catch below-fold issues."
},
{
"name": "browser_list_webmcp_tools",
"title": "Browser List Webmcp Tools",
"description": "List WebMCP tools exposed by the current page via document.modelContext (after navigate). Returns tool names, descriptions, and optional input schemas."
},
{
"name": "browser_navigate",
"title": "Browser Navigate",
"description": "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_until=domcontentloaded (default on Remote Browser) and timeout=30000 for slow pages."
}
]It is best when your agent needs to drive Chrome on the same machine as your code — localhost dev servers, internal apps, and interactive UI debugging without exposing anything to the public internet.
Local Browser runs Chrome on your machine through MCPBundles Desktop, so it reaches localhost directly. Remote Browser runs Chrome in the cloud and needs a tunnel for localhost.
© 2026 ThinkChain Inc. All rights reserved.
Capabilities
53 tools · 1 groups
24 read · 29 write
Connector pricing
Yes. Desktop supervises the secure tunnel between your agent and local Chrome. Install it on the Mac or PC where Chrome runs and keep it open while you automate.
Yes. Screenshot tools return visual content that agents can inspect, which is useful for layout review, visual QA, and debugging UI states.
Some websites register structured tools on the page itself. After you navigate, your agent can list those tools and call them directly — useful when the site exposes search or data APIs without clicking through the DOM.
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/browser. Authentication is handled automatically.
Local Browser provides 53 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.
Local Browser uses API Key. Local Browser requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
Other MCP servers in this category from the directory index