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.225,425,474 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.36 npmMIT
- AlicenseNot gradedqualityAmaintenanceRemote 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 are clearly distinct (account, usage, logs, sessions, performance, search, map, crawl, export, function, smartscraper, profiles, link_connect, link_checkout). The main ambiguity is between browserless_smartscraper, browserless_crawl, and browserless_map, which all involve scraping/discovery, though their descriptions do differentiate single-page vs multi-page vs URL discovery. browserless_agent and browserless_function also overlap in executing browser automation, but one is a persistent session and the other is custom Puppeteer code.
All tools use the browserless_ prefix with a descriptive noun (agent, skill, sessions, link_checkout, link_connect, performance, account, usage, logs, smartscraper, function, export, map, crawl, profiles, search). The pattern is consistent, though 'link_checkout' and 'link_connect' use a verb-ish noun while others are plain nouns, and 'smartscraper' is a compound word rather than a simple noun. Minor deviations but overall predictable.
16 tools is on the higher end but appropriate for a browser automation platform that covers session control, scraping, crawling, search, account management, and Stripe Link integration. Each tool serves a distinct capability area, though a few could be consolidated (e.g., smartscraper/crawl/map could arguably be one tool with modes).
The tool surface covers the core browser automation lifecycle well: driving a session (browserless_agent), custom code (browserless_function), scraping (smartscraper), crawling (crawl), mapping (map), search, export, performance audits, account/usage/logs, sessions, profiles, and Stripe Link. Minor gaps: there's no dedicated tool for managing browser profiles beyond listing them (no create/delete), and no explicit tool for managing API keys, but these are peripheral to the main purpose.