Browserbase MCP Server

Created By
browserbasea year ago
Allow LLMs to control a browser with Browserbase and Stagehand
Overview

what is Browserbase MCP Server?

Browserbase MCP Server is a cloud-based automation server that leverages the Model Context Protocol (MCP) to enable integration between large language model (LLM) applications and external data sources and tools. It allows LLMs to perform web-related tasks like taking screenshots and executing JavaScript.

how to use Browserbase MCP Server?

To get started, refer to the README files provided in the Browserbase and Stagehand directories on the GitHub repository. Users can set up the server to automate interactions with web pages through the cloud.

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.
  • JavaScript Execution: Run custom JavaScript in the browser context.
  • Web Interaction: Navigate, click, and fill forms effortlessly.

use cases of Browserbase MCP Server?

  1. Building AI-powered integrated development environments (IDEs) that require web access.
  2. Enhancing chat interfaces by enabling them to fetch real-time data from web pages.
  3. Creating custom AI workflows that need to interact with web pages for data collection or manipulation.

FAQ from Browserbase MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that facilitates seamless integration between LLM applications and external tools/data sources.

  • Can I use any LLM with Browserbase MCP Server?

Yes, it supports multiple models including OpenAI's GPT-4 and Anthropic's Claude-3.5 Sonnet.

  • Is the Browserbase MCP Server open source?

Yes, the project is open source, and contributions are welcome. Join the Slack community for support.

Project Info
Featured
Created At
a year ago
Updated At
a year ago
Author Name
browserbase
Star
1831
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)

20 hours ago
Gpt Scrambler

2 days ago