Browserbase MCP Server

Created By
thesimsguya year ago
Overview

What is Browserbase MCP Server?

Browserbase MCP Server is a cloud-based solution that enables seamless integration between large language models (LLMs) and external data sources through the Model Context Protocol (MCP). It allows LLMs to interact with web pages, execute JavaScript, and automate browser tasks.

How to use Browserbase MCP Server?

To get started, refer to the documentation for Browserbase MCP or Stagehand MCP. Users can control cloud browsers, extract data, and perform web interactions through the provided APIs.

Key features of Browserbase MCP Server?

  • Browser Automation: Control and orchestrate cloud browsers.
  • Data Extraction: Extract structured data from any webpage.
  • Console Monitoring: Track and analyze browser console logs.
  • Screenshots: Capture full-page and element screenshots.
  • Web Interaction: Navigate, click, and fill forms with ease.

Use cases of Browserbase MCP Server?

  1. Automating data extraction for web scraping tasks.
  2. Enhancing AI-powered applications with real-time web data.
  3. Testing web applications by simulating user interactions.

FAQ from Browserbase MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that facilitates the integration of LLM applications with external data sources and tools.

  • Is Browserbase MCP Server open source?

Yes, it is open source, and contributions are welcome.

  • What kind of models does it support?

It supports multiple models, including OpenAI's GPT-4 and Anthropic's Claude-3.7 Sonnet.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
thesimsguy
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago