Skip to content

Browser Use vs shelf-smoke — url smoke / headless QA

Browser Use is a freemium MCP server for browser automation. shelf-smoke — url smoke / headless QA is an MCP server for browser automation.

  • Browser Use is open source; shelf-smoke — url smoke / headless QA is not.
  • Browser Use is best for fill in web forms automatically.
What it is
Browser Use is a freemium MCP server for browser automation.
shelf-smoke — url smoke / headless QA is an MCP server for browser automation.
Best for
Fill in web forms automatically
Kind
MCP server
MCP server
Pricing
Freemium
Platforms
API, CLI, Web, self-hosted
Runs
Locally or Remotely
Remotely
GitHub stars
121K
Last commit
Nov 2026
License
MIT
Open source
Good for
Fill in web forms automatically; Extract data from websites; Run shopping or checkout tasks with an agent

What Browser Use does

  • Web agents

    Send a task and receive structured JSON results.

  • Stealth cloud browsers

    Hosted browsers meant to get past bot checks, billed per hour.

  • Browser Harness

    A tool aimed at coding agents such as Claude Code and Codex.

  • Open-source package

    MIT-licensed Python package installable from PyPI.

  • Remote MCP endpoint

    A streamable-http MCP server is available alongside the stdio package.

  • Enterprise options

    On-prem, US or EU cloud, SOC 2 Type II and HIPAA on enterprise plans.

What shelf-smoke — url smoke / headless QA does

    Browser Use vs shelf-smoke — url smoke / headless QA: questions

    What is the difference between Browser Use and shelf-smoke — url smoke / headless QA?

    Browser Use is a freemium MCP server for browser automation. shelf-smoke — url smoke / headless QA is an MCP server for browser automation. Browser Use is open source; shelf-smoke — url smoke / headless QA is not.