open-browser-mcp-server

Created By
handoinga year ago
Open the browser and visit the specified website address
Overview

what is open-browser-mcp-server?

open-browser-mcp-server is a tool designed to automate the process of opening a web browser and navigating to a specified website address.

how to use open-browser-mcp-server?

To use open-browser-mcp-server, simply run the server and provide the desired website URL as a parameter. The server will then open the default web browser and navigate to the specified address.

key features of open-browser-mcp-server?

  • Automates browser opening and navigation to specified URLs.
  • Simple and easy-to-use interface for web automation tasks.
  • Built with JavaScript, making it accessible for developers familiar with the language.

use cases of open-browser-mcp-server?

  1. Automating testing of web applications by opening specific URLs.
  2. Quickly accessing frequently visited websites without manual input.
  3. Integrating with other automation tools to enhance web interaction capabilities.

FAQ from open-browser-mcp-server?

  • What programming language is open-browser-mcp-server built with?

open-browser-mcp-server is built with JavaScript.

  • Is there a graphical user interface for this tool?

No, it is a command-line tool designed for automation purposes.

  • Can I use it to open multiple websites at once?

Currently, it supports opening one website at a time.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
handoing
Star
0
Language
JavaScript
License
-
Tags

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