"A server similar to Browser-Use MCP Server" matching MCP servers:

This gives Claude Desktop access to browser automation tools for web scraping, form filling, and more.

Enables AI agents to autonomously operate web browsers through the Model Context Protocol, including navigating pages, clicking, typing, filling forms, and extracting structured data.

Launches multiple Browser-Use agents to automatically test websites for UI bugs, broken links, accessibility issues, and other technical problems on both live and localhost sites.

Enables any MCP-connected agent to drive a browser by reading each page as an indexed action-space table and performing one guarded operation on a numbered target, refusing and refreshing when the page changes instead of retrying selectors.

Facilitates browser automation with custom capabilities and agent-based interactions, integrated through the browser-use library.

Enables AI agents to control a persistent Chrome browser through a local daemon, with Jev performing routine actions and the host agent handling reasoning, text, and verification.

Provides AI clients with deterministic Playwright-driven browser control, enabling navigation, interaction, screenshots, and inspection of rendered HTML, computed styles, console diagnostics, and font audits without an embedded LLM or API key.

Enables browser automation through MCP clients like Claude or Cursor, using the client's existing LLM without requiring an additional API key.

Enables AI agents to control and automate browser actions through an MCP server deployed on Heroku. Supports programmatic browser automation with natural language tasks across multiple LLM providers.

An MCP server for automating browser tasks using the Browser Use API. Provides tools to run, monitor, and manage browser automation tasks.

An MCP server that connects any MCP client (like Claude or Cursor) with the browser using browser-use, allowing clients to utilize existing LLMs without requiring additional API keys.

Enables the Pi coding agent to drive Chrome through DevTools, providing browser automation tools, persistent or isolated profiles, screenshots, page analysis, and bundled agent policies.

Enables an MCP-capable AI chat to control selected tabs in a separate persistent Chromium browser, protected by OAuth, per-tab grants, and local approvals.

Enables MCP-driven browser automation from any MCP client by pairing with a Chrome extension, translating tool calls into WebSocket commands to drive Chrome without an Electron host.

Enables AI assistants to browse websites, extract information, fill forms, interact with pages, and execute multi-step web tasks autonomously.

Enables coding agents to drive a real Chrome browser to complete natural-language web tasks and return evidence for verification.

A Windows-only MCP server for controlling a real browser using native screenshots, Windows accessibility, and node-interception mouse/keyboard input, without CDP or Playwright.

Enables browser automation using Python scripts, offering operations like taking webpage screenshots, retrieving HTML content, and executing JavaScript.

AI-driven browser automation server that implements the Model Context Protocol to enable natural language control of web browsers for tasks like navigation, form filling, and visual interaction.

Enables AI agents to interact with web browsers using natural language, featuring automated browsing, form filling, vision-based element detection, and structured JSON responses for systematic browser control.

An MCP server that enables AI assistants to control a web browser through natural language commands, allowing them to navigate websites and extract information via SSE transport.

A FastMCP server that enables browser automation through natural language commands, allowing Language Models to browse the web, fill out forms, click buttons, and perform other web-based tasks via a simple API.

Enables MCP-capable agent CLIs on macOS to reuse an installed, unmodified OpenAI Browser Runtime to drive a connected Chrome or Edge browser (or a host's in-app browser backend) through js, js_reset, and turn_ended tools. It stays a thin bridge that preserves the Runtime's approval and security boundaries, failing closed when the client cannot handle approval requests.

MCP server enabling LLMs to perform browser tasks via SSE transport, allowing clients like Cursor.ai and Claude to open websites and interact with web content through natural language commands.

Enables AI agents to automate web browsers using local Ollama models via the Model Context Protocol, supporting tasks like web search, data extraction, and e-commerce analysis through natural language commands.

Enables any agent to drive a dedicated Chromium instance through MCP, including opening and reading pages, taking steps, logging in via a password vault, downloading/uploading files, and replaying saved routines. It also gates sensitive actions behind approvals and can use client certificates or one-time card data for official procedures.

MCP server that wraps sendblue-browser-use's HTTP API, providing tools to control a stealth-patched Chromium browser with persistent sessions, navigation, screenshots, and script execution.

Enables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.

Enables AI agents to control a Playwright-driven browser through natural-language instructions, including page interaction and live browser task execution.

Provides an MCP server for macOS that allows agents to control a managed browser with accessibility-first actions, visible cursor, and screenshot return.