Bright Data MCP

Created By
luminati-ioa year ago
A powerful Model Context Protocol (MCP) server that provides an all-in-one solution for public web access.
Overview

What is Bright Data MCP?

Bright Data MCP is a powerful Model Context Protocol (MCP) server that provides an all-in-one solution for public web access, enabling clients to make informed decisions based on web data.

How to use Bright Data MCP?

To use Bright Data MCP, set up an account on brightdata.com, obtain your API key, and configure your MCP server with the necessary environment variables. You can also integrate it with various MCP clients like Claude Desktop.

Key features of Bright Data MCP?

  • Provides access to public web data for decision-making.
  • Supports multiple MCP clients for flexibility.
  • Allows customization of proxy zones for enhanced functionality.

Use cases of Bright Data MCP?

  1. Querying real-time data such as market caps or weather forecasts.
  2. Integrating with AI agents for enhanced data-driven decision-making.
  3. Automating web scraping tasks for various applications.

FAQ from Bright Data MCP?

  • Can I use Bright Data MCP for free?

New users receive free credits for testing, with pay-as-you-go options available.

  • What types of queries can I run?

You can run queries related to market data, weather forecasts, and more, leveraging public web information.

  • How do I troubleshoot timeouts?

Adjust the timeout settings in your agent to accommodate slower-loading web pages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
luminati-io
Star
54
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago