browserless-mcp
OfficialRelated Servers
Alternatives to browserless-mcp
- AlicenseAqualityDmaintenanceA server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots without requiring screenshots or vision models.226,403,349 npm1Apache 2.0
Related Servers
- FlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server for browser automation with stealth patches, offering 50 tools for navigation, scraping, and session configuration. Runs via Docker and supports remote control from any MCP client.-
- AlicenseAqualityBmaintenanceMCP server for browser automation with anti-detection. Scout pages, find elements, interact with websites, and monitor network traffic from any AI client that supports the Model Context Protocol.211MIT
- AlicenseNot gradedqualityBmaintenanceA high-performance MCP server for browser automation via Chrome DevTools Protocol, enabling fast, low-cost, and anti-bot web interactions.23 npmMIT
- AlicenseAqualityDmaintenanceMCP server for headless browser automation via Puppeteer, with stealth anti-detection and Playwright-format ARIA snapshots.38 npmMIT
- AlicenseNot gradedqualityBmaintenanceRemote MCP server for web scraping with anti-bot evasion. Provides stealth HTTP fetching, headless browser with Cloudflare bypass, CSS selectors, YouTube transcripts, and Markdown conversion.1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes the Pinchtab browser API for token-efficient web scraping, change detection, and automated testing workflows.15-
TDQS
Scored across 16 tools
Most tools map to distinct Browserless API areas (performance, account, usage, sessions, logs, profiles, link wallet), but there is real overlap among browserless_agent, browserless_function, browserless_smartscraper, browserless_export, browserless_crawl, and browserless_search for fetching/scraping page content. The descriptions mostly resolve this by steering single-page vs. multi-page vs. custom-code vs. interactive-agent workflows, so confusion is limited but possible.
Every tool uses the browserless_ prefix followed by snake_case, with predictable resource/action names such as browserless_performance, browserless_account, browserless_link_connect, and browserless_link_checkout. The convention is consistent throughout.
At 16 tools, the set is slightly above the typical 3-15 sweet spot, but the breadth of the Browserless platform justifies separate tools for auditing, exporting, scraping, crawling, searching, custom functions, agent sessions, account stats, logs, profiles, and Stripe Link. There is little obvious filler.
The surface covers the main Browserless workflows well: scraping, crawling, search, custom functions, interactive agent automation, performance audits, export, account usage, sessions, logs, profiles, and Link checkout. Minor gaps remain around direct profile creation/deletion and dedicated screenshot/PDF/download tools, though other tools partially compensate.