"Information about browser usage or browser use statistics" matching MCP servers:

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.

Reliable, scalable browser infrastructure for AI agents. Route, pool, and failover across any browser provider. 8 built-in browser tools using raw Chrome CDP - navigate, screenshot, snapshot, interact, evaluate. Zero-config with auto Chrome detection & concurrent sessions support

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.

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.

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.

Headed Playwright browser MCP server with persistent profile, providing 23 tools for full browser automation while masking PII data.

MCP server to drive browser-migrate operations from Claude, enabling exporting, importing, and migrating browser profiles (bookmarks, history, tabs) between browsers.

Enables AI agents to control local Chrome/Edge browser profiles through MCP, including tab groups, bounded DOM actions, observations, and optional encrypted credential use.

MCP server that lets AI agents use your real browser as an API, accessing any website with your login state, no keys or scrapers needed.

A MCP server that allows AI assistants to interact with the browser, including getting page content as markdown, modifying page styles, and searching browser history.

An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.

A token-efficient MCP server for Chrome browser automation that uses direct CDP and accessibility-tree-based references for stable element selection across DOM changes.

Gives AI agents a compact, semantic interface to the browser, returning structured page snapshots with stable element IDs instead of raw DOM. Enables agents to navigate, interact, and extract information from web pages efficiently.

Lets MCP agents drive VS Code's integrated browser tab that the user shares with them: opening pages, taking accessibility snapshots and screenshots, clicking, typing, scrolling, dragging and reading console and network activity with real trusted input. It also maps a picked element back to the source file, line and column that rendered it, so an agent receives the same selection the developer clicked.

MCP server for headless browser automation via Puppeteer, with stealth anti-detection and Playwright-format ARIA snapshots.

MCP server that lets AI assistants browse the web through your real Chrome with your cookies, sessions, and fingerprint, avoiding bot detection and CAPTCHAs. Enables web browsing, content extraction, and multi-step workflows via persistent tabs.

MCP server for AI browser automation with tools for navigation, actions, data extraction, and scripting, supporting local and cloud execution.

Lets any number of concurrent Claude Code sessions drive a Firefox browser through the Browser Control extension by funneling every session's commands over a single shared port via a background daemon and private unix socket. Sessions no longer have to compete for a limited pool of extension ports, and requests stay isolated through per-request correlation ids.

A headless browser MCP server that allows AI agents to fetch web content and perform Google searches without API keys, supporting various output formats like Markdown, JSON, HTML, and text.

Enables AI agents to inspect and modify Chrome state directly through extension APIs, listing tabs and windows and moving or reordering tabs within and across windows. Operations are validated and never simulate mouse/keyboard input, steal focus, or activate tabs implicitly.