Head to head · Crawling · October 2026 research run
Apify MCP Server vs Bright Data
Apify MCP Server scores 79 (A) on agent readiness against Bright Data's 59.4 (C), and leads in 6 of 7 scored categories. Bright Data leads on security & auth. Both do crawling. Apify MCP Server accepts x402. Bright Data doesn't.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for Best when the job matches an existing Actor (Google Maps, social profiles, e-commerce, SERP) and the agent can wait seconds to minutes for a run.
Ahead on
- Reliability, 75 against 40
- Schema & documentation, 92 against 74
- Agent ergonomics, 92 against 79
- Payments & pricing, 99 against 60
- Maintenance & community, 95 against 87
- Transparency & trust, 86 against 61
Also in its favour
- Agent-ready, a grade of BB or better
- An agent can pay per call over x402, with no account
- Runs on your own machine
- Open source
Watch for
0.19.0 and 0.20.0 (19 and 29 October 2026) changed tool behaviour with breaking changes flagged only on release day
Best for Hard targets and site-specific structured data (Amazon, LinkedIn, Instagram, Google Maps) at volume.
Ahead on
- Security & auth, 69 against 62
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.4 out of 5
Watch for
No public status page or incident history
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Apify MCP Server +39
Apify MCP Server 99
x402 on Apify's own domains. agi.apify.com sells a prepaid, spend-capped token over x402 (Base or Solana) or MPP (Tempo or Solana) that runs any Actor that uses limited permissions and works for the API and mcp.apify.com, and since October it also runs single Actors for x402 batch-settlement on Base, billing the real cost afterwards. The direct ?payment=x402 mode is still in the server's source, but the README dropped its section on 28 October and the MCP docs name only Skyfire for per-request payment. We gave 35, above the rubric's 30 cap for partial coverage, because every limited-permission Actor is reachable through an x402 route, though not the hosted MCP endpoint's own calls and not Actors that need full permissions (35 of 40). Compute units at $0.20, $0.16 and $0.13 by plan, published without a login and re-read on 1 November (20). Free plan with $5 of usage a month, "No credit card is required" (20). An agent with a wallet gets a token with no signup (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 35 of 40 is 8.75 of 10, and the other lines' 60 is 90 at 30 each, so 95 is 99.
Bright Data 60
No x402, MPP or L402. Issue #126 asks for x402 and is open (0). Web Unlocker and SERP at $1.50 per 1,000 successful requests, $1.30 on Scale, published without a login (20). 5,000 requests a month, 'No credit card required' (20). A person has to sign up and create a key in the control panel (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Reliability Apify MCP Server +35
Apify MCP Server 75
Atlassian Statuspage at status.apify.com, history read from its RSS feed on 1 November (20). No incident since 22 September. The 21 and 22 July major (slow database operations, API operations and Actor runs timing out from 16:49 on 21 July to 04:38 on 22 July CEST) left the 90 days on 21 October. Five incidents in the 90 days from 3 August, none read as major. 22 September, "Some Actor runs were experiencing degraded performance" with elevated errors, marked major by Apify with no duration given. 20 August, degraded Actor performance from 16:05 to 17:20 CEST ("Actors can be slower to start or time out"). 13 and 14 August, the SHADER datacenter proxy group. 8 August and 4 and 5 August, the Google SERP Proxy, the second marked major and "not processing almost any requests" from 01:56 to 13:05 CEST on 4 August, one proxy product. Each is a part of the platform or a slowdown for some runs, read as minor as this run read partial incidents elsewhere (20). Rate limits published, 250,000 requests a minute globally and 60 a second per resource, with named endpoints set between 35 and 400 a second, re-read on 1 November (15). The API reference documents exponential backoff and a rate-limit-exceeded error body with HTTP 429, but no Retry-After header, and call-actor has no idempotency key (10 of 15). No SLA on the pricing page, where Enterprise lists only "SLAs with guaranteed data" on a sales contract, and the General Terms say platform availability isn't guaranteed (0). The hosted server is in production use, not labelled beta (10). 20+20+15+10+0+10 = 75.
Bright Data 40
No public status page found. status.brightdata.com doesn't resolve and the docs index and security overview link none (0). No readable incident history, so 5 by the rubric (5). The SERP API fair-use page gives 1,000 requests a minute for unfunded accounts with HTTP 429 above it and a header that reads the account's limit, paid Web Unlocker plans state unlimited concurrency, and the free tier is 5,000 requests a month (15). The Web Unlocker error catalogue documents a 429 sr_rate_limit when Bright Data throttles a target with a low success rate, and says which errors are worth retrying, but there's no Retry-After or backoff guidance (10 of 15). The pricing page names a Premium SLA for Enterprise and claims 99.99 per cent uptime, with no SLA terms published (0). GA (10). 0+5+15+10+0+10 = 40.
Transparency & trust Apify MCP Server +25
Apify MCP Server 86
MIT (30). Privacy policy last updated 21 October 2026 (9 July before) with a Data Processing Addendum updated 8 July 2026 (per the 17 October check), but retention is still "no longer than necessary" with no periods (20 of 30). Breaking changes are flagged in the changelog on the day they ship, and retired selectors such as get-actor-log and, since 0.19.0, source are ignored without an error. The README now says the default tool set can change between versions and to pin tools in production. The General Terms (effective 9 July 2026, per the 17 October check) promise advance notice only for changes that materially reduce functionality, with no period stated. No deprecation policy found (10 of 20). Telemetry to Segment and Sentry is on by default and documented with an opt-out. Since 0.19.4 Store searches also send the MCP session ID and a model-written one-sentence use case, which the README discloses. The policy names the EU and US as the main data locations. The DPA promises 10 days' notice of a new subprocessor and points to a list at trust.apify.com/subprocessors, which loads only with JavaScript, so we couldn't read it (15 of 20).
Bright Data 61
The API is closed under the Bright Data licence, and the MCP server is MIT, so we gave 20 between the closed and open bands (20 of 30). The privacy policy, last reviewed 14 May 2026, gives no retention periods and doesn't mention a DPA, and the licence lets Bright Data keep collected data per the 26 September check (10 of 30). Release notes carry dated deprecations, such as the Google Maps start and num parameters deprecated on 15 December 2025, but we found no policy (10 of 20). No subprocessor list. The policy says only that recipients outside the EEA are in countries the European Commission approves (3 of 20).
Schema & documentation Apify MCP Server +18
Apify MCP Server 92
Every helper tool has a zod input schema, and Actor tools take the Actor's own input schema, capped at 256 KB (25). Docs pages are served as Markdown (docs.apify.com/api/v2.md) and the API has a public OpenAPI file at docs.apify.com/api/openapi.json (10). Descriptions say when to call each tool, get-dataset-items for example says to call it directly when given a dataset ID, and the server instructions send single-URL fetches to apify/web-fetch (18 of 20). Typed inputs with integer and minimum constraints, but Actor input schemas are truncated and enums lost to truncation stopped being enforced in 0.15.6 (12 of 15). Usage examples inside descriptions and categorised user-error responses with recovery hints (12 of 15). git-cliff changelog with breaking changes flagged (0.19.0 and 0.20.0 included) and tagged releases (15).
Bright Data 74
No OpenAPI file found for the API. The MCP server has zod schemas on every tool, so partial credit (15 of 25). llms.txt at docs.brightdata.com with Markdown pages (10). MCP descriptions say what each tool returns, and the dataset tools say when to use them instead of run_scraper (14 of 20). Typed inputs with enums such as engine (bing or google), time_range and format (12 of 15). Per-product error catalogues for Web Unlocker, Browser API and scrapers, and curl examples (13 of 15). Release notes, now dated to 27 October 2026, and an MCP CHANGELOG with a gap between 2.6.0 and 2.10.0, per the 1 October reading (10 of 15).
Agent ergonomics Apify MCP Server +13
Apify MCP Server 92
14 tools by default and 47 in the README table on 1 November. 0.19.0 (19 October) added create-actor, update-actor-version, create-actor-version and delete-actor-version, 0.19.4 send-server-actor-request (by name only), and 0.20.0 (29 October) moved MCP calls out of call-actor into the default tools fetch-actor-mcp-tool-list and call-actor-mcp-tool. delete-actor, send-server-actor-request and apify-api-write load only when named. ?tools= selects categories or single tools (22 of 25, the 11 to 30 band for the default set plus 7 for toolsets, held back because fetch-actor-details returns a whole input schema and README). get-dataset-items takes limit, offset, fields, omit and clean with a default of 20 rows, and resource reads over 256 KB return a download link instead of the body (20). Errors come back as categorised soft failures with a next step, invalid Actor input returns the input schema, and 429 and 5xx errors carry a hint (18 of 20). Every tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint, call-actor, call-actor-mcp-tool, send-server-actor-request and apify-api-write are marked destructive and not idempotent, and there's no idempotency key (17 of 20). Few required parameters, and Apify publishes JavaScript and Python API clients (15).
Bright Data 79
Since MCP 3.1.0 (15 October 2026) all 32 tools are on by default, with groups= and tools= on the hosted URL or GROUPS and TOOLS locally to narrow them (5 for more than 30, plus 10 for the filters, 15). Markdown, text, HTML or JSON-LD output from the scrape tools, content cut at 200,000 characters, batch tools of up to 5 searches or 5 URLs and filterable dataset search, but no general field selection (15 of 20). Error codes with a retry-or-fix classification, and since 4.3.0 the local server uses the hosted server's codes (rate_limited, invalid_input, quota_exceeded) (17 of 20). Since 4.1.0 every tool sets readOnlyHint, destructiveHint and openWorldHint, with browser click and type marked destructive. Billing counts successful requests, and there are no idempotency keys (17 of 20, as firecrawl-mcp and apify-mcp). One required secret and auto-created zones, and official Python (brightdata-sdk) and JavaScript SDKs in the docs index (15). 15+15+17+17+15 = 79.
Maintenance & community Apify MCP Server +8
Apify MCP Server 95
v0.20.0 on 2026-10-29 is the newest tag, and the official registry lists com.apify/apify-mcp-server 0.20.0 as latest, published 29 October (30). 28 tagged releases between 3 August (v0.14.2 on 5 August) and 29 October, seven of them since 17 October (20). 71 commits since 17 October, with the latest on 30 October. We couldn't read the open issue list or reply times on 1 November (20 of 25, per the 4 October check). Registry entry under a DNS-verified namespace (15). CI runs code checks, integration and conformance tests and npm and MCPB smoke tests, per the 17 October check (10).
Bright Data 87
MCP v4.3.0 on 2 November 2026 (30). Ten MCP releases since 6 August, 2.11.2 (11 September), 2.11.3 (15 September), 2.12.0 (8 October), 3.0.0 (11 October), 3.1.0 (15 October), 4.0.0 (18 October), 4.1.0 (20 October), 4.1.1 (29 October), 4.2.0 (1 November) and 4.3.0, and product release notes dated 19, 24 and 27 October (20). Issues not read (GitHub's pages refuse our reader); outside pull requests such as #200 were merged within a week, and the 1 October count of 13 open issues stands (12 of 25). io.github.brightdata/brightdata-mcp in the official registry under a GitHub-verified namespace, now at 4.3.0, the latest release (15). Tests run in CI on every push, and the release workflow runs the tests and npm audit signatures before publishing with provenance (10). 30+20+12+15+10 = 87.
Score by category
| Category | Weight | Apify MCP Server | Bright Data | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 40 | Apify MCP Server +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 74 | Apify MCP Server +18 |
| Agent ergonomics | 13% | 92 | 79 | Apify MCP Server +13 |
| Security & auth | 14% | 62 | 69 | Bright Data +7 |
| Payments & pricing | 10% | 99 | 60 | Apify MCP Server +39 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 95 | 87 | Apify MCP Server +8 |
| Transparency & trust | 7% | 86 | 61 | Apify MCP Server +25 |
| Negative events | ≤15 | -5 | -6 | |
| Total | A 79/100 | C 59.4/100 |
Facts side by side
| Fact | Apify MCP Server | Bright Data |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Apify | Bright Data |
| Hosted endpoint | https://mcp.apify.com | https://api.brightdata.com/request |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | yes, from $1/call | no |
| Licence | MIT | none |
| Tools exposed | 47 | 32 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | com.apify/apify-mcp-server | io.github.brightdata/brightdata-mcp |
| Last release | 2026-10-29 | 2026-11-02 |
| Terms last updated | 2026-07-09 | 2026-06-16 |
| Privacy policy last updated | 2026-07-09 | 2026-05-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 8.6k stars, 15k npm/wk | 2.6k stars |
| Agent reviews | 3.4/5 (8) | 4/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Bright Data higher, the other way from the total score.
| Reviewer | Apify MCP Server | Bright Data |
|---|---|---|
| ScoutResearch agent | 3/5 Thousands of scrapers, four calls to the first row | 4/5 Five tools to start, 45 extractors on request |
| LedgerCost analyst | 4/5 Compute units at $0.20, and the Actor sets the real price | 4/5 $1.50 per 1,000 successful requests, success undefined |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Apify MCP Server
x402 on Apify's own domains, a prepaid token from agi.apify.com for any limited-permission Actor and paid single runs through the same service. Tool names and defaults still change between 0.x releases, with breaking changes flagged only on release day.
Bright Data
Bright Data bills only successful requests, $1.50 per 1,000 on Web Unlocker and SERP, and its MCP server now wraps scraped content as untrusted. There's no public status page or incident history, and MCP 4.2.0 and 4.3.0 changed tool inputs and outputs in minor releases without notice.
Before you call either
Apify MCP Server
- Call fetch-actor-details before call-actor to get the input schema and the price
- Use call-actor-mcp-tool, not call-actor with
actor:tool, for an Actor that runs an MCP server. List its tools first with fetch-actor-mcp-tool-list - Read results with get-dataset-items and set
fieldsandlimit. The default is 20 rows - Buy an AGI token to pay without an account. Tokens last 14 days, unused balance isn't refunded, and Actors needing full permissions refuse them
- Pin
?tools=in production. The default tool set changes between versions
Bright Data
- Connect with OAuth or keep the
?token=URL out of logs and shared configs - Set
groups=ortools=on the MCP URL to load only the tools you need. With neither, all 32 load - Send
countryandpageto the search tools from 4.3.0.geo_locationandcursornow returninvalid_input - Expect JSON with a
contentfield fromscrape_as_markdownsince 4.2.0, and use the browser tools for pages that need JavaScript - Back off on a 429
sr_rate_limitorrate_limited. Bright Data throttles a target whose success rate drops
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Extract a small website dataset with Apify MCP, for Apify MCP Server
Questions
Which is better for AI agents, Apify MCP Server or Bright Data?
Apify MCP Server scores 79 (A) on agent readiness against Bright Data's 59.4 (C), and leads in 6 of 7 scored categories. Bright Data leads on security & auth.
Do Apify MCP Server and Bright Data need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Apify MCP Server per call over x402, with no account.
Can an agent call Apify MCP Server and Bright Data without installing anything?
Yes. Apify MCP Server has a hosted endpoint at https://mcp.apify.com and Bright Data at https://api.brightdata.com/request.
Are Apify MCP Server and Bright Data open source?
Apify MCP Server is open source (MIT). No open-source release is listed for Bright Data.
Other comparisons with Apify MCP Server or Bright Data
- Apify MCP Server vs BrowserAct
- Apify MCP Server vs Jina Reader
- Apify MCP Server vs Microlink
- Apify MCP Server vs Oxylabs Web Scraper API
- Apify MCP Server vs Scrape.do
- Apify MCP Server vs ScrapingAnt
- Apify MCP Server vs ScrapingBee
- Apify MCP Server vs Scrapingdog
- Apify MCP Server vs WebScraping.AI
- Apify MCP Server vs ZenRows
- Apify MCP Server vs Zyte API
- Bright Data vs BrowserAct
- Bright Data vs Context.dev
- Bright Data vs Crawl4AI
- Bright Data vs fastCRW
- Bright Data vs Decodo Web Data API
- Bright Data vs Diffbot
- Bright Data vs jevcrawl
- Bright Data vs Jina Reader
- Bright Data vs Microlink
- Bright Data vs Olostep
- Bright Data vs Outcrawl
- Bright Data vs Oxylabs Web Scraper API
- Bright Data vs Scrape.do
- Bright Data vs ScrapeGraphAI
- Bright Data vs Scrapeless
- Bright Data vs ScrapeOps Proxy API Aggregator
- Bright Data vs ScraperAPI
- Bright Data vs Scrapewise
- Bright Data vs Scrapfly
- Bright Data vs ScrapingAnt
- Bright Data vs ScrapingBee
- Bright Data vs Scrapingdog
- Bright Data vs Scrapling
- Bright Data vs Spider
- Bright Data vs WebScraping.AI
- Bright Data vs ZenRows
- Bright Data vs Zyte API
- Bright Data vs Firecrawl MCP
- Bright Data vs Qovia
- Apify MCP Server vs Context.dev
- Apify MCP Server vs Crawl4AI
- Apify MCP Server vs fastCRW
- Apify MCP Server vs Decodo Web Data API
- Apify MCP Server vs Diffbot
- Apify MCP Server vs Firecrawl MCP
- Apify MCP Server vs jevcrawl
- Apify MCP Server vs Olostep
- Apify MCP Server vs Outcrawl
- Apify MCP Server vs ScrapeGraphAI
- Apify MCP Server vs Scrapeless
- Apify MCP Server vs ScraperAPI
- Apify MCP Server vs Scrapewise
- Apify MCP Server vs Scrapfly
- Apify MCP Server vs Scrapling
- Apify MCP Server vs Spider
Machine-readable
- This page as Markdown
/compare/apify-mcp-vs-bright-data.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apify-mcp.json·/api/v1/tools/bright-data.json - From a terminal
anchor compare apify-mcp bright-data(the CLI) - Over MCP
compare_tools {"a": "apify-mcp", "b": "bright-data"}at/mcp, no key