Skip to main content
Glama
AndrewEstopinan

Bright Data MCP Server

by AndrewEstopinan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Bright Data MCP Server

No user-submitted related servers found.

    Related Servers

    • FineData MCP Server

      quality-network
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to scrape any website by providing tools for JavaScript rendering, antibot bypass, and automatic captcha solving. It supports synchronous, asynchronous, and batch scraping operations with built-in proxy rotation.
      5
      207 npm
      MIT

    • Browser MCP Server

      feedmepos
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate a real, anti-bot-aware browser through Zyte API for navigating pages, clicking, typing, scrolling, taking screenshots, searching, and extracting structured data, with automatic proxy rotation and ban avoidance.
      18 npm
      -

    • webscout-mcp

      wxs-lang
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to perform web searches, fetch and extract page content, and crawl sites with caching, rate limiting, and robots.txt compliance, all without needing API keys.
      11
      675 PyPI
      1
      MIT

    • ScrapeOps MCP Server

      ScrapeOps
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to browse the web, bypass anti-bots, render JavaScript, take screenshots, and perform structured data extraction using the ScrapeOps Proxy API.
      3
      5 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 57 tools

    Disambiguation5/5

    Every tool has a clearly distinct target and action, from smart_scrape/unlocker_scrape (with explicit cost/fallback differences) to the large web_data_* family, where each tool is bound to a specific platform and entity. Even with 57 tools, there is no real ambiguity because descriptions precisely delimit the use case.

    Naming Consistency3/5

    Naming is consistent within families: web_data_* for structured data, smart_* for cost-aware fetching, unlocker_* for paid requests, and web_scraper_* for datasets. However, the overall set mixes these prefixes with standalone names like serp_search, browser_scrape, parse_feed, check_robots, and replay_har, so no single predictable convention governs the whole server.

    Tool Count2/5

    At 57 tools, the server far exceeds the typical well-scoped 3-15 tool range. While each endpoint offers distinct value, the sheer volume makes selection harder and suggests the server is a sprawling catalog rather than a focused toolkit, potentially overwhelming agents.

    Completeness5/5

    The server covers the entire scraping lifecycle: free vs paid fetch, async jobs, batching, crawling, search, structured data for dozens of major sites, diff/extract, robots checking, and HAR replay. Paired trigger/get-result tools ensure no dead ends, and the domain appears fully addressed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources