Browser-use MCP Client

Created By
Linzo99a year ago
A MCP client for browser-use
Overview

What is Browser-use MCP Client?

Browser-use MCP Client is a modern React application designed to provide a user-friendly interface for interacting with Model Context Protocol (MCP) servers through Server-Sent Events (SSE).

How to use Browser-use MCP Client?

To use the Browser-use MCP Client, clone the repository, install the dependencies, and start the development server. Ensure you have a running MCP server for connection.

Key features of Browser-use MCP Client?

  • Real-time communication with direct SSE connection to MCP servers.
  • Interactive UI built with React and Tailwind CSS.
  • Theme support for light and dark modes.
  • Live browser screenshot previews from MCP server responses.
  • Persistent chat history with clear message threading.
  • Request management features including canceling in-progress requests.
  • Easy server connection configuration.

Use cases of Browser-use MCP Client?

  1. Interacting with MCP servers for real-time data.
  2. Managing browser automation tasks through a user-friendly interface.
  3. Monitoring and visualizing server responses in real-time.

FAQ from Browser-use MCP Client?

  • What are the prerequisites for using the Browser-use MCP Client?

You need Node.js (v18 or later), pnpm, and a running MCP server.

  • Can I customize the UI?

Yes! The application supports theme customization.

  • Is there a demo available?

Yes! A demo is available on the project's GitHub page.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Linzo99
Star
7
Language
TypeScript
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