MyMCPTools
Guides8 min read

Best MCP Servers for Web Scraping & Browser Automation in 2026

Top MCP servers for web scraping, browser automation, and data extraction. Playwright, Puppeteer, Browserbase, Firecrawl, and more — with setup guides.

By MyMCPTools Team·

Web scraping and browser automation are tasks where MCP servers add enormous value. Instead of writing brittle scraping scripts and debugging them manually, you can direct your AI to navigate pages, extract data, and handle edge cases — all through natural language. The AI runs the browser commands, you describe the outcome.

Here are the best MCP servers for web scraping and browser automation in 2026.

1. Playwright MCP Server — The Power Option

Playwright is Microsoft's browser automation framework and the gold standard for serious scraping and testing workflows. The Playwright MCP server gives your AI complete browser control: navigation, interaction, screenshot capture, and JavaScript execution.

Capabilities:

  • Full browser control across Chromium, Firefox, and WebKit
  • Network interception — capture API calls made by pages
  • Screenshot and PDF generation
  • Form interaction and file uploads
  • Handling SPAs, infinite scroll, and dynamic content
  • Anti-bot handling via stealth mode

Best for: Complex scraping jobs, SPAs that require JavaScript execution, and test automation that verifies your application's real browser behavior.

Setup:

npx @modelcontextprotocol/server-playwright

2. Puppeteer MCP Server — Chromium-Focused Automation

Puppeteer is Google's Chromium automation library. Its MCP server provides similar capabilities to Playwright but focuses exclusively on Chromium-based browsers. It's lighter-weight for straightforward use cases and has a huge ecosystem of community extensions.

When to choose Puppeteer over Playwright:

  • You're specifically targeting Chrome/Chromium behavior
  • Your project already uses Puppeteer and you want MCP access to the same driver
  • You need lightweight headless Chrome operations

3. Browserbase MCP Server — Cloud Browser Automation

Browserbase runs browsers in the cloud — no local Chromium installation required. This is ideal for scraping jobs that need residential IP addresses, long-running sessions, or scale beyond what a single machine can handle.

Key advantages:

  • Cloud-hosted browsers that bypass IP-based bot detection
  • Session persistence across multiple scraping tasks
  • Parallel execution for high-volume data collection
  • No local browser management or update headaches

Best for: Production scraping operations, e-commerce price monitoring, and any workflow where local browser limitations are a bottleneck.

4. Stagehand MCP Server — AI-Powered Browser Automation

Stagehand is a Browserbase-backed framework that adds an AI layer on top of browser automation — it can figure out how to interact with page elements based on natural language descriptions, even when element selectors change. The MCP server brings this capability into your AI workflow.

How Stagehand differs: Traditional scraping breaks when a website redesigns its UI. Stagehand's AI-backed selector finding adapts automatically. This makes it particularly valuable for scraping production sites that update frequently.

5. Firecrawl MCP Server — Fast Structured Extraction

Firecrawl is purpose-built for AI-ready web scraping — it crawls websites and returns clean, structured content in markdown format that LLMs can directly consume. No JavaScript parsing, no HTML cleaning, just ready-to-use text.

Key features:

  • Full-site crawling with configurable depth
  • Automatic content extraction (removes navigation, ads, boilerplate)
  • Markdown output optimized for LLM consumption
  • Structured data extraction with schema support
  • JavaScript rendering for SPAs

Best for: Content aggregation, competitor analysis, knowledge base building from documentation sites, and any workflow where you need clean text rather than raw HTML.

6. Fetch MCP Server — Simple URL Content Fetching

For basic content extraction without browser automation overhead, the Fetch MCP server is the simplest option. It retrieves web pages and converts them to LLM-friendly format. No JavaScript rendering, but perfect for static sites and API documentation.

When to use Fetch over Playwright:

  • The target site doesn't require JavaScript execution
  • You need fast, lightweight page retrieval
  • You're fetching structured content like RSS feeds or API documentation

7. Apify MCP Server — Enterprise Scraping Platform

Apify is an enterprise-grade scraping platform with thousands of pre-built actors (scrapers) for popular sites. The Apify MCP server gives your AI access to run these actors on demand — scrape LinkedIn, Amazon, Google Maps, and hundreds of other sites using pre-tested, production-grade scrapers.

Best for: Teams that need reliable scraping of major platforms without building and maintaining scrapers from scratch.

8. Exa Search MCP Server — Neural Search for Web Data

Exa's neural search API finds semantically relevant content across the web — not just keyword matches, but meaning-based retrieval. The MCP server makes it trivial to pull high-quality, relevant web content into your AI's context for research, fact-checking, and competitive intelligence.

Choosing the Right Tool for Your Use Case

Here's a quick decision framework:

  • Static sites, docs, articles → Fetch or Firecrawl
  • SPAs, login-required pages, complex interaction → Playwright or Puppeteer
  • Production scraping at scale, anti-bot issues → Browserbase or Apify
  • Sites that change frequently → Stagehand (AI selector adaptation)
  • Semantic research / finding relevant content → Exa

Ethical and Legal Considerations

Before scraping any website:

  • Check the site's robots.txt and Terms of Service
  • Respect rate limits — don't hammer servers with rapid requests
  • Avoid scraping personal data that could create GDPR/privacy liabilities
  • Consider whether the data owner has a first-party API you should use instead

Browse all browser automation MCP servers and search MCP servers on MyMCPTools.

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

🌍

Playwright MCP Server (ExecuteAutomation)

ExecuteAutomation's Playwright MCP Server is a community-maintained browser automation server (5,500+ GitHub stars) distinct from Microsoft's official microsoft/playwright-mcp — it leans further into test generation and visual workflows rather than pure accessibility-tree navigation. Beyond standard navigate/click/fill/screenshot tools, it can generate Playwright test code from a live browsing session, scrape full page content and structured data, execute arbitrary JavaScript in the page context, and drive API testing (GET/POST/PUT/PATCH/DELETE requests) alongside the browser tools. A standout feature is 143 real device presets for responsive testing — a single call like playwright_resize({ device: "iPhone 13" }) swaps in the correct viewport, user-agent, touch support, and device pixel ratio, and natural-language prompts like "test on iPad landscape" work directly through Claude. Install via `npm install -g @executeautomation/playwright-mcp-server`, Smithery, mcp-get, or the one-line `claude mcp add --transport stdio playwright npx @executeautomation/playwright-mcp-server` for Claude Code; VS Code one-click installers are also published. No API keys are required — it launches and drives a local Chromium/Firefox/WebKit browser directly. Choose this over Microsoft's official server when you specifically need auto-generated Playwright test scripts, JS execution, or device-emulation testing; choose Microsoft's for pure lightweight accessibility-tree page navigation. One maintenance fact the listings omit, checked against GitHub and npm on 2026-08-15: this repository has not been pushed since 2025-12-13 and npm 1.0.12 was published 2025-12-12, with 32 issues open. It is neither archived nor deprecated, so nothing warns you at install time — it installs, connects and works while its Playwright dependency drifts, whereas Microsoft's server ships continuously. Weigh the codegen, 143-preset device emulation and HTTP request tools against running an eight-month-old build. Note also that headless defaults to false on playwright_navigate, so it opens a visible browser window unless told otherwise, and that stdio-mode logging goes only to ~/playwright-mcp-server.log to keep the JSON-RPC stream clean.

Local📘
🌍

Puppeteer MCP Server

browser automation over MCP — navigate, click, fill, screenshot and run JavaScript in a real Chromium instance — but the first thing to know is that this server is archived. It was one of Anthropic's original reference servers and now lives in modelcontextprotocol/servers-archived, a repository GitHub reports as archived with no commits since May 2025. The npm package @modelcontextprotocol/server-puppeteer is still installable and still runs, and its last publish is from the same period, so treat it as frozen rather than broken: no new features, no security patches, no dependency bumps on Puppeteer itself. For new work the maintained successors are Microsoft's Playwright MCP server and ExecuteAutomation's Playwright MCP server, both of which cover the same ground with active releases. If you are maintaining an existing integration, the surface is small and easy to reason about. Seven tools: `puppeteer_navigate` (takes an optional `launchOptions` object mirroring PuppeteerJS LaunchOptions — changing it restarts the browser — and an `allowDangerous` flag that must be true before flags like `--no-sandbox` or `--disable-web-security` are accepted), `puppeteer_screenshot` (CSS selector for element shots, 800x600 default, optional `encoded` for a base64 data URI instead of binary content), `puppeteer_click`, `puppeteer_hover`, `puppeteer_fill`, `puppeteer_select`, and `puppeteer_evaluate` for arbitrary JavaScript in the page context. It also exposes two resource types the tools alone do not give you: `console://logs` for the live browser console stream and `screenshot://<name>` for captured PNGs. The README carries an explicit security caution worth repeating — the browser runs on your own machine, so it can reach local files and internal IP addresses, and should not be pointed at untrusted pages while sensitive data is reachable. The npx install opens a visible browser window; the Docker image `mcp/puppeteer` runs headless Chromium instead.

Local
🌍

Browserbase MCP Server

Browserbase MCP and Stagehand MCP are the same server under two names, and this catalog lists both because people search for both — this page is the platform view, /servers/stagehand covers the natural-language automation layer that runs inside it. What Browserbase supplies is the browser itself: a headless Chrome session running in Browserbase's cloud rather than on the machine your agent is on, which is the reason to use it at all. The session is a real, addressable browser with its own residential-proxy and stealth configuration and a recorded replay you can watch afterwards, so an agent's browsing survives being run from a datacenter IP, and a failed run is debuggable after the fact instead of being a black box. Nothing renders on the developer's machine, so a long-running agent is not tied to a desktop staying awake. Browserbase's recommendation is the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they operate it and absorb the model inference that the instruction-following tools require. Clients without HTTP transport connect via npx mcp-remote https://mcp.browserbase.com/mcp. Self-hosting installs @browserbasehq/mcp-server-browserbase from npm and needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID from your dashboard. Six tools are exposed — start and end for session lifecycle, navigate, act, observe and extract — and they are documented in detail on the Stagehand entry, because the act/observe/extract trio is Stagehand's model rather than Browserbase's. One thing to know before self-hosting: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now says it is kept for historical reference and should not be read as representative of the current production service. The npm package still installs and the star count on this page belongs to that archived repo; the hosted endpoint is the path Browserbase actually maintains.

Local✓
🌍

Stagehand (Browserbase) MCP Server

Stagehand is the natural-language layer of the same server documented at /servers/browserbase — one endpoint, two search terms; read that page for session, proxy and stealth behaviour, and this one for how the instruction-following tools actually work. It is cloud browser automation driven by natural-language instructions rather than CSS selectors, running on Browserbase's hosted browsers via the Stagehand framework. The package name has changed and the old one is gone: `@browserbasehq/mcp-stagehand` is not on the npm registry, and the server that replaced it is published as @browserbasehq/mcp-server-browserbase (v2.4.3). Browserbase's own recommendation is to skip the local install entirely and use the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they run it and cover the Gemini inference costs that Stagehand's instruction-following needs. Clients without HTTP transport can reach the same endpoint through `npx mcp-remote https://mcp.browserbase.com/mcp`. Six tools are exposed, and they map onto Stagehand's model rather than a raw browser API: start and end open and close a Browserbase session, navigate takes a URL, act performs an action described in plain language, observe returns the actionable elements on the current page so an agent can plan before it clicks, and extract pulls structured data out according to an instruction. The observe-then-act split is the reason this holds up better than selector-based automation on pages that change layout between runs. Worth knowing before you self-host: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now states it is retained for historical purposes and should not be treated as representative of Browserbase's current production service. The npm package still installs, but the hosted endpoint is the maintained path.

Local✓
🌍

Firecrawl MCP Server

The Firecrawl MCP server gives your AI assistant the ability to crawl, scrape, and extract structured data from any website — turning raw HTML into clean, LLM-ready Markdown or JSON in seconds. Built by the Firecrawl team, it exposes tools for single-page scraping, deep site crawls (following internal links), and batch URL extraction, all with JavaScript rendering handled automatically so dynamic content is never missed. Developers use it to automate competitive research, build live knowledge bases, extract pricing tables, monitor documentation changes, or feed structured web data into RAG pipelines — all through natural-language prompts without writing a single scraper script. The Firecrawl MCP server handles rate limiting, retries, and proxy rotation behind the scenes. Authentication requires a Firecrawl API key (free tier available). Install with: npx firecrawl-mcp. Works with Claude Desktop, Cursor, VS Code, and any MCP-compatible client. With Firecrawl, any public webpage becomes a structured data source your AI can reason over, compare, and act on — making it the go-to MCP server for web data extraction workflows.

Live
🌐

Fetch

Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.

Local✓
🌍

Apify MCP Server

The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.

Auth required✓
🔍

Exa MCP Server

Exa's official MCP server connects AI assistants to a search engine purpose-built for AI, using neural embeddings to match on meaning rather than keywords so agents get clean, ready-to-use content instead of a page of blue links to re-parse. The default tool set covers web_search_exa for quick topical lookups and web_search_advanced_exa for full control over domains, date ranges, and content filters, plus specialized tools for code_search (searching real-world code and GitHub), company_research (building company profiles, competitor lists, and financials), crawling/web_fetch (pulling clean content from a specific URL), people_search and linkedin_search (public professional-profile lookups), and deep_researcher_start/check for long-running multi-step research tasks backed by Exa's Research API. The server is hosted at https://mcp.exa.ai/mcp — no local process to run — and connects via one-line setup in Cursor, VS Code, Claude Code, Claude Desktop (available as a native Connector), Codex, OpenCode, Windsurf, and Antigravity, authenticated with an EXA_API_KEY from the Exa dashboard. Tool exposure is tunable per client via a ?tools= query parameter on the endpoint URL, letting teams ship narrow, purpose-built configurations (e.g. company-research-only or LinkedIn-only agents) instead of exposing the full surface, and Exa ships ready-made Claude Skills/agent definitions for common patterns like company research and people search with built-in query-variation and token-isolation guidance.

Live✓
🔍

Brave Search MCP Server

The Brave Search MCP Server is the official server from Brave that gives AI assistants privacy-first web search through the independent Brave Search API — no tracking, no profiling, and results drawn from Brave's own web index rather than Google or Bing. It exposes five distinct tools that map directly to the Brave Search API endpoints: brave_web_search for general queries with pagination, freshness filters, and safe-search controls; brave_local_search for businesses, restaurants, and points of interest with automatic location filtering; brave_news_search for recent articles and current events; brave_image_search for image discovery; and brave_video_search for finding videos across the web. Authentication uses a single BRAVE_API_KEY (free tier available at brave.com/search/api) or a mounted BRAVE_API_KEY_FILE for Docker-secret setups. Install in Claude Desktop, Cursor, Windsurf, or VS Code with one npx command and choose stdio or streamable-HTTP transport. Because Brave operates its own crawler and index, the Brave Search MCP server is a strong choice for developers who want an alternative to Google-dependent search tools, need reproducible non-personalized results, or care about data privacy in agent workflows — Claude can pull fresh web context, verify facts, and research topics without leaking queries to ad-tech pipelines.

Local✓

📚 More from the Blog

Guides

Best MCP Servers for Developers in 2026: The Complete Guide

Discover the top MCP servers that every developer should know about. From filesystem access to database queries, these Model Context Protocol servers supercharge your AI coding workflow.

8 min readGuides

Best MCP Servers for Data Engineering: Database, ETL & Analytics

Top MCP servers for data engineers and analysts. Connect your AI to PostgreSQL, BigQuery, Snowflake, and more for AI-powered data workflows.

7 min readTutorials

Getting Started with MCP: A Beginner's Guide to Model Context Protocol

New to MCP? Learn what Model Context Protocol is, how it works, and how to set up your first MCP server in under 5 minutes. Complete beginner's guide.

10 min read