"browser use" matching MCP servers:

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.

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

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.

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.

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.

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

Enables autonomous agents to anchor browser elements from vision inputs, providing stable DOM references resilient to click drift for reliable computer-use automation.

Enables AI agents to anchor visible on-screen elements to stable DOM targets, preventing click drift during browser computer-use automation.

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.

An MCP server that enables remote observation and control of a Chromium browser via a WebSocket relay, supporting DOM, CDP, and native OS automation for local or LAN-based AI agents.

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.

Browser-based research MCP server that drives a real Chromium browser via patched Playwright to access JavaScript-rendered content, dynamic tables, and login-walled dashboards. It provides tools for visiting URLs to extract DOM text and screenshots, and for performing structured data extraction using Anthropic Claude Sonnet.