Bright MCP

Agent-oriented Bright Data capabilities over MCP, built on Bun. The seven-tool all profile separates search, ranked source discovery, exact reading, extraction, research, maintained dataset discovery, and execution. It pages complete pages and upstream snapshots as resources and renders structured results in a transient React MCP workbench.

The full seven-tool contract remains at /mcp. Entitlement-aligned installs can use stable three- or two-tool surfaces at /mcp/web, /mcp/deep-lookup, or /mcp/marketplace; Scraping Browser is a separate four-tool surface at /mcp/browser. Tool lists never change after initialization based on a probe.

Install

Set BRIGHTDATA_API_KEY in the client environment first.

Plugin

Codex:

codex plugin marketplace add dunkeln/bright_mcp --ref main
codex plugin add bright@bright

Claude Code:

claude plugin marketplace add dunkeln/bright_mcp
claude plugin install bright@bright

MCP

Codex:

codex mcp add bright --url https://bright-mcp.onrender.com/mcp \
  --bearer-token-env-var BRIGHTDATA_API_KEY

Claude Code:

claude mcp add --transport http bright https://bright-mcp.onrender.com/mcp \
  --header "Authorization: Bearer ${BRIGHTDATA_API_KEY}"

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "bright": {
      "url": "https://bright-mcp.onrender.com/mcp",
      "headers": { "Authorization": "Bearer ${env:BRIGHTDATA_API_KEY}" }
    }
  }
}

The key is forwarded over HTTPS and kept only in a bounded in-memory cache; Bright MCP does not persist it. Available live capabilities follow the products enabled on that Bright Data account.

Choose the narrowest surface your account and workflow need:

Choose among the seven data tools by intent:

See SETUP.md for local development, credentials, live checks, and hosted authorization.

Related MCP server: WebQuest MCP

Benchmarks

Both MCPs completed 29 of 30 workflows; the meaningful separation begins after completion, in the quality and efficiency of the answer.

Bright leads every blind-scored quality dimension, with its clearest gains in fulfillment, grounding, source quality, and actionability.

The blind judge preferred Bright 17 times versus 3 for BrightData, while preserving 10 genuine ties.

Structured Marketplace work is where Bright's richer answers most clearly repay their token budget; simpler web tasks remain the efficiency target.

Bright converts tokens into successful Marketplace execution efficiently, while the web workflows show where tighter routing can recover more value.

Bright batches known-page reading into one call and makes Marketplace discovery explicit; historical search follow-ups expose the routing behavior now being tightened.

At the same 97% completion rate, Bright MCP delivered 4.51/5 judged quality versus 3.78/5, used slightly fewer tokens, and won the blind preference 17–3 with 10 ties. Method and tables · current-entitlements Acquire + Operate profile · openrouter/anthropic/claude-haiku-4.5 · 10 runs/case · 2026-07-22.

WIP capabilities

Recurring delivery is intentionally excluded from the current benchmark score. Bright MCP can discover and run datasets, but it cannot yet create a durable refresh schedule; the case returns when it can execute delivery instead of only describing that boundary.

A/B