Best ScrapingBee MCP Server MCP Server Alternatives 2026

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

Free and open-source by Anthropic. Fetches web content directly — no API key or paid service required.

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.

The MCP server is free and open-source. Apify platform: Free tier with $5/mo platform credits. Starter: $49/mo. Scale: $499/mo. Enterprise: Custom pricing.

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.

The MCP server is free and open-source. Browserbase: Free tier with limited browser sessions. Paid plans for higher volume. See official pricing for current rates.

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.

The MCP server is free and open-source. Firecrawl: Free tier with 500 credits. Hobby: $16/mo (3,000 credits). Standard: $83/mo. Growth: $333/mo.

The Notion MCP Server is the official integration from Notion that connects AI assistants directly to your Notion workspace via the Notion REST API. With 4,580+ GitHub stars, it is the canonical MCP tool for bringing Notion's knowledge management capabilities into Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. The server exposes a rich set of tools: search your entire workspace by keyword and return matching pages and databases; retrieve full page content and block trees; create new pages inside any parent page or workspace section; update, append, or delete block content on existing pages; list all databases your integration has access to; query database entries with filter and sort parameters; retrieve individual blocks or nested children by block ID; and add comments to pages. Authentication uses a Notion integration token — create an internal integration at notion.so/my-integrations, share specific pages or databases with it, and set NOTION_TOKEN in your environment (the older OPENAPI_MCP_HEADERS form still works). Install with a single npx command. The Notion MCP Server is especially powerful for AI workflows that span documentation retrieval, project planning, and knowledge capture — Claude can read product specs from Notion, draft new pages from conversation output, log structured data into databases, and search across thousands of notes without any manual copy-paste.

The MCP server is free and open-source. Notion: Free for personal use. Plus: $10/user/mo. Business: $18/user/mo. Enterprise: Custom pricing.

The HubSpot MCP Server is HubSpot's hosted, official Model Context Protocol endpoint for Smart CRM data, reachable at https://mcp.hubspot.com and authorised with OAuth 2.0 — there is no package to install and no token to paste into a config file. Access is scoped by a HubSpot user-level app: you create one with read (and optionally write) scopes for the CRM objects you want an assistant to reach, then complete the OAuth flow from inside your client. Read and write coverage spans contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, subscriptions and lists, plus engagements — calls, emails, meetings, notes and tasks — and the associations between them. Organisational context (users, teams, reporting structures, owners, roles, seats) and marketing content (campaigns and their metrics, landing pages, website pages, blog posts) are read-only. Custom Sensitive Data Properties and Personal Health Information are excluded regardless of scopes. Two other things share the name and are commonly confused with this one: the Developer MCP server, installed locally with `hs mcp setup` from the HubSpot CLI and aimed at building HubSpot apps rather than querying CRM records, which requires Developer Platform v2025.2; and the original May 2025 public beta, an npm package configured with a private-app access token, which is what most third-party setup guides still describe. The server remains in beta and HubSpot advises experimenting in a developer sandbox and reviewing every write confirmation, since an LLM will occasionally propose a change to a system of record that it should not.

The MCP server is free and open-source. HubSpot CRM: Free tier available. Starter: $20/mo. Professional: $890/mo. Enterprise: $3,600/mo.

The Stripe MCP server is Stripe's official Model Context Protocol integration, and the first thing to know is that it is not a package you install — it is a remote server Stripe hosts at https://mcp.stripe.com, and the documented connection mechanism is OAuth, not an API key. For Claude Code that is `claude mcp add --transport http stripe https://mcp.stripe.com/` followed by `claude /mcp` to complete consent; Cursor and VS Code take the bare URL, and ChatGPT accepts it as a custom connector on Pro, Plus, Business, Enterprise and Education accounts. An administrator has to enable MCP access in the Dashboard first, separately for sandbox and for live mode, which is the usual cause of a connection that refuses to authorise. Rather than one tool per endpoint, four generic tools carry most of the surface — stripe_api_search, stripe_api_details, stripe_api_read and stripe_api_write — so the tool schemas do not consume the context window, alongside dedicated create_refund, get_stripe_account_info, stripe_report, stripe_implementation_planner and search_stripe_documentation tools, plus a Treasury balance summary in public preview. Supported API methods span customers, charges, refunds, PaymentIntents, Checkout Sessions, invoices, subscriptions, coupons, promotion codes, products, prices, payment links, disputes, webhook endpoints, balance and balance transactions, payouts, tax settings and registrations, and Issuing. Clients that cannot do OAuth pass a restricted API key as a bearer token; Connect platforms acting as a connected account must use a restricted key plus a Stripe-Account header, since OAuth cannot express that. Sessions are revocable from Dashboard user settings under OAuth sessions, and Stripe recommends human confirmation of tools given prompt-injection risk.

The MCP server is free and open-source. Stripe: Pay-per-transaction pricing at 2.9% + 30¢ per card charge. No monthly fees. Volume discounts available.

Turns your GraphQL API into MCP tools, from Apollo GraphQL itself. Rather than exposing a raw schema and hoping the model composes valid queries, the Apollo MCP Server takes a set of GraphQL operations you explicitly define and publishes each one as a named MCP tool, so an AI client calls a curated, tested operation instead of assembling ad-hoc GraphQL. It sits in front of a graph and needs three things configured: the graph itself, the operation definitions that become tools, and a config file describing how the server runs — all documented on the Apollo docs site. There are three ways to run it, which is the practical thing searchers want: the standalone binary (install with `curl -sSL https://mcp.apollo.dev/download/nix/latest | sh` on macOS/Linux, or the PowerShell `iwr` one-liner on Windows, and pin a version by swapping `latest` for e.g. `v1.17.0`); the Rover CLI via `rover dev --mcp <config>` (Rover v0.37+) to run the server alongside a local graph during development; and the Apollo Runtime Container, which can run the MCP server and the Apollo Router together in one container. Because tools map to predefined operations, you get persisted-query-style safety — the model cannot invent expensive or unauthorized queries — plus custom scalar handling, auth passthrough, CORS and error-handling controls covered in the config reference. Built in Rust, MIT licensed, actively maintained (released continuously), and the canonical repo is `apollographql/apollo-mcp-server`. This is the right MCP server for anyone exposing a GraphQL or federated supergraph to Claude, Cursor, or any MCP client. Compatible with all MCP-compliant clients over stdio and HTTP transports.

This MCP server is free and open-source. Check the GitHub repository for details.

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.

Free and open-source MCP server. Puppeteer is free and open-source by Google. No service costs — runs locally.

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.

Free and open-source MCP server. Playwright is free and open-source by Microsoft. No service costs — runs locally.