The Web MCP is your gateway to giving AI assistants true web capabilities. No more outdated responses, no more - I can't access real-time information - just seamless, reliable web access that actually works.
Brightdata the web mcp is your gateway to giving ai assistants true web capabilities. no more outdated responses, no more - i can't access real-time information - just seamless, reliable web access that actually works.. The official Brightdata MCP server provides AI agents with standardized access to Brightdata's services, enabling powerful automation and integration capabilities that enhance developer productivity and streamline workflows.
This official MCP server is maintained and verified by Brightdata, ensuring reliability, security, and up-to-date functionality. Unlike community-maintained servers, this official integration provides long-term support, comprehensive documentation, and direct vendor assistance. The server is hosted on brightdata.com, guaranteeing secure and reliable access to Brightdata's services.
Whether you're building AI-powered applications, automating workflows, or enhancing your development tools, the Brightdata MCP server provides a standardized way to connect AI agents with Brightdata's extensive platform capabilities. This integration enables natural language interactions with Brightdata, making it easier than ever to leverage Brightdata's features through AI assistants like Claude, ChatGPT, and Cursor.
https://mcp.brightdata.com/mcpGo to Settings → Cursor Settings
Click "Add new global MCP Server"
Paste the MCP configuration into mcp.json and restart
Or manually add to your mcp.json:
{
"mcpServers": {
"brightdata": {
"url": "https://mcp.brightdata.com/mcp"
}
}
}The official Brightdata MCP server enables AI agents to:
These capabilities make it easy for AI agents to work with Brightdata as part of a larger automation strategy, enabling seamless integration between AI assistants and your existing tools.
The Brightdata MCP server provides 63 tools for AI agents to interact with the platform. Use the search below to find specific tools.
| Tool Name | Description |
|---|---|
extract | Scrape a webpage as Markdown and convert it to structured JSON using AI sampling, with an optional custom extraction prompt. |
scrape_as_html | Scrape a single webpage with advanced extraction and return the HTML response body. Handles sites protected by bot detection or CAPTCHA. |
scrape_as_markdown | Scrape a single webpage with advanced extraction and return Markdown. Uses Bright Data's unlocker to handle bot protection and CAPTCHA. |
scrape_batch | Scrape up to 10 webpages in one request and return an array of URL/content pairs in Markdown format. |
scraping_browser_click_ref | Click an element using its ref from the latest ARIA snapshot; requires a ref and human-readable element description. |
scraping_browser_get_html | Return the HTML content of the current page; avoid the full_page option unless head or script tags are required. |
scraping_browser_get_text | Return the text content of the current page's body element. |
scraping_browser_go_back | Navigate the active scraping-browser session back to the previous page and report the new URL and title. |
scraping_browser_go_forward | Navigate the active scraping-browser session forward to the next page and report the new URL and title. |
scraping_browser_navigate | Open or reuse a scraping-browser session and navigate to the provided URL, resetting tracked network requests. |
scraping_browser_network_requests | List the network requests recorded since page load with HTTP method, URL, and response status for debugging. |
scraping_browser_screenshot | Capture a screenshot of the current page; supports optional full_page mode for full-length images. |
scraping_browser_scroll | Scroll to the bottom of the current page in the scraping-browser session. |
scraping_browser_scroll_to_ref | Scroll the page until the element referenced in the ARIA snapshot is in view. |
scraping_browser_snapshot | Capture an ARIA snapshot of the current page listing interactive elements and their refs for later ref-based actions. |
scraping_browser_type_ref | Fill an element identified by ref from the ARIA snapshot, optionally pressing Enter to submit after typing. |
scraping_browser_wait_for_ref | Wait until an element identified by ARIA ref becomes visible, with an optional timeout in milliseconds. |
search_engine | Scrape search results from Google, Bing, or Yandex. Returns SERP results in JSON for Google and Markdown for Bing/Yandex; supports pagination with the cursor parameter. |
search_engine_batch | Run up to 10 search queries in parallel. Returns JSON for Google results and Markdown for Bing/Yandex. |
session_stats | Report how many times each tool has been called during the current MCP session. |
web_data_amazon_product | Quickly read structured Amazon product data. Requires a valid product URL containing /dp/. Often faster and more reliable than scraping. |
web_data_amazon_product_reviews | Quickly read structured Amazon product review data. Requires a valid product URL containing /dp/. Often faster and more reliable than scraping. |
web_data_amazon_product_search | Retrieve structured Amazon search results. Requires a search keyword and Amazon domain URL; limited to the first page of results. |
web_data_apple_app_store | Quickly read structured Apple App Store app data. Requires a valid App Store app URL. Often faster and more reliable than scraping. |
web_data_bestbuy_products | Quickly read structured Best Buy product data. Requires a valid Best Buy product URL. Often faster and more reliable than scraping. |
web_data_booking_hotel_listings | Quickly read structured Booking.com hotel listing data. Requires a valid Booking.com listing URL. Often faster and more reliable than scraping. |
web_data_crunchbase_company | Quickly read structured Crunchbase company data. Requires a valid Crunchbase company URL. Often faster and more reliable than scraping. |
web_data_ebay_product | Quickly read structured eBay product data. Requires a valid eBay product URL. Often faster and more reliable than scraping. |
web_data_etsy_products | Quickly read structured Etsy product data. Requires a valid Etsy product URL. Often faster and more reliable than scraping. |
web_data_facebook_company_reviews | Quickly read structured Facebook company reviews data. Requires a valid Facebook company URL and review count. Often faster and more reliable than scraping. |
web_data_facebook_events | Quickly read structured Facebook events data. Requires a valid Facebook event URL. Often faster and more reliable than scraping. |
web_data_facebook_marketplace_listings | Quickly read structured Facebook Marketplace listing data. Requires a valid Marketplace listing URL. Often faster and more reliable than scraping. |
web_data_facebook_posts | Quickly read structured Facebook post data. Requires a valid Facebook post URL. Often faster and more reliable than scraping. |
web_data_github_repository_file | Quickly read structured GitHub repository file data. Requires a valid GitHub file URL. Often faster and more reliable than scraping. |
web_data_google_maps_reviews | Quickly read structured Google Maps reviews data. Requires a valid Google Maps URL and optional days_limit (default 3). Often faster and more reliable than scraping. |
web_data_google_play_store | Quickly read structured Google Play Store app data. Requires a valid Play Store app URL. Often faster and more reliable than scraping. |
web_data_google_shopping | Quickly read structured Google Shopping product data. Requires a valid Google Shopping product URL. Often faster and more reliable than scraping. |
web_data_homedepot_products | Quickly read structured Home Depot product data. Requires a valid homedepot.com product URL. Often faster and more reliable than scraping. |
web_data_instagram_comments | Quickly read structured Instagram comments data. Requires a valid Instagram URL. Often faster and more reliable than scraping. |
web_data_instagram_posts | Quickly read structured Instagram post data. Requires a valid Instagram post URL. Often faster and more reliable than scraping. |
web_data_instagram_profiles | Quickly read structured Instagram profile data. Requires a valid Instagram profile URL. Often faster and more reliable than scraping. |
web_data_instagram_reels | Quickly read structured Instagram reel data. Requires a valid Instagram reel URL. Often faster and more reliable than scraping. |
web_data_linkedin_company_profile | Quickly read structured LinkedIn company profile data. Requires a valid LinkedIn company URL. Often faster and more reliable than scraping. |
web_data_linkedin_job_listings | Quickly read structured LinkedIn job listings data. Requires a valid LinkedIn jobs URL or search URL. Often faster and more reliable than scraping. |
web_data_linkedin_people_search | Quickly read structured LinkedIn people search data. Requires a LinkedIn people search URL. Often faster and more reliable than scraping. |
web_data_linkedin_person_profile | Quickly read structured LinkedIn people profile data. Requires a valid LinkedIn profile URL. Often faster and more reliable than scraping. |
web_data_linkedin_posts | Quickly read structured LinkedIn posts data. Requires a valid LinkedIn post URL. Often faster and more reliable than scraping. |
web_data_reddit_posts | Quickly read structured Reddit post data. Requires a valid Reddit post URL. Often faster and more reliable than scraping. |
web_data_reuter_news | Quickly read structured Reuters news data. Requires a valid Reuters news article URL. Often faster and more reliable than scraping. |
web_data_tiktok_comments | Quickly read structured TikTok comments data. Requires a valid TikTok video URL. Often faster and more reliable than scraping. |
web_data_tiktok_posts | Quickly read structured TikTok post data. Requires a valid TikTok post URL. Often faster and more reliable than scraping. |
web_data_tiktok_profiles | Quickly read structured TikTok profile data. Requires a valid TikTok profile URL. Often faster and more reliable than scraping. |
web_data_tiktok_shop | Quickly read structured TikTok Shop product data. Requires a valid TikTok Shop product URL. Often faster and more reliable than scraping. |
web_data_walmart_product | Quickly read structured Walmart product data. Requires a product URL containing /ip/. Often faster and more reliable than scraping. |
web_data_walmart_seller | Quickly read structured Walmart seller data. Requires a valid Walmart seller URL. Often faster and more reliable than scraping. |
web_data_x_posts | Quickly read structured X (Twitter) post data. Requires a valid X post URL. Often faster and more reliable than scraping. |
web_data_yahoo_finance_business | Quickly read structured Yahoo Finance company profile data. Requires a valid Yahoo Finance business URL. Often faster and more reliable than scraping. |
web_data_youtube_comments | Quickly read structured YouTube comments data. Requires a valid YouTube video URL and optional num_of_comments (default 10). Often faster and more reliable than scraping. |
web_data_youtube_profiles | Quickly read structured YouTube channel profile data. Requires a valid YouTube channel URL. Often faster and more reliable than scraping. |
web_data_youtube_videos | Quickly read structured YouTube video metadata. Requires a valid YouTube video URL. Often faster and more reliable than scraping. |
web_data_zara_products | Quickly read structured Zara product data. Requires a valid Zara product URL. Often faster and more reliable than scraping. |
web_data_zillow_properties_listing | Quickly read structured Zillow property listing data. Requires a valid Zillow listing URL. Often faster and more reliable than scraping. |
web_data_zoominfo_company_profile | Quickly read structured ZoomInfo company profile data. Requires a valid ZoomInfo company URL. Often faster and more reliable than scraping. |
Last updated: January 27, 2026 at 12:26 PM
Extract content from websites and convert it to structured formats. Perfect for research, competitive analysis, and data collection.
Monitor websites for changes, track competitor pricing, or collect data from multiple sources automatically.
Convert web pages to markdown or JSON for easier processing, documentation, or content migration.
Visit https://brightdata.com, create an account, and generate an API key from your dashboard. Most tools offer a free tier to get started, making it easy to begin using the Brightdata MCP server.
Yes, this MCP server is officially provided and maintained by Brightdata. The endpoint https://mcp.brightdata.com/mcp is hosted on their official domain brightdata.com, ensuring reliability and security.
The Brightdata MCP server requires appropriate API credentials and permissions based on the operations you want to perform. Check the documentation for specific permission requirements.
Yes, you can configure the same MCP server across Cursor, Claude Desktop, Cline, and other MCP-compatible clients simultaneously. Each client maintains its own configuration.
The MCP server itself is free to use, but you may need a Brightdata account and API access, which may have its own pricing tiers. Check https://brightdata.com for current pricing information.
The Brightdata MCP server enables AI agents to extract and process web content. The Web MCP is your gateway to giving AI assistants true web capabilities. No more outdated responses, no more - I can't access real-time information - just seamless, reliable web access that actually works. This allows you to interact with Brightdata's platform through natural language commands in your AI assistant.
Ensure your API key is correctly configured and your network allows outbound connections to brightdata.com. Verify that the MCP endpoint URL https://mcp.brightdata.com/mcp is accessible from your network.
Verify your API key is valid and has not expired. Generate a new key from https://brightdata.com if needed. Make sure you're using the correct authentication method as specified in the documentation.
Check Brightdata's status page for any ongoing incidents. Try restarting your MCP client and verify that the server endpoint is correct. If issues persist, consult the official documentation or support channels.
Explore other official MCP servers that work well with Brightdata:
The Model Context Protocol (MCP) is an open standard that enables AI models to securely connect to external APIs, tools, and data sources. This official MCP server from Brightdata provides standardized access to their services, allowing AI agents to interact with Brightdata's platform seamlessly.
To manage all your MCP servers in one place, use Apigene's MCP Gateway, which provides centralized management, security, and governance for all your MCP server connections.
Learn more about MCP in our complete guide or browse our FAQ for common questions.