Brightdata MCP vs Webhound

A side-by-side look at the Brightdata MCP and Webhound MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Brightdata MCP logoBrightdata MCPSearch & Data Extraction · Local subprocess (stdio)Discover, extract, and interact with the web - one interface powering automated access across the public internet.69GreatAuth: api key required
W
WebhoundSearch & Data Extraction
Budgeted web research and datasets with cited outputs, evidence packs, and controllable effort.37FairAuth: not declared

Verdict: choose Brightdata MCP for search & data extraction work as a local process; choose Webhound for search & data extraction. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Brightdata MCP logoChoose Brightdata MCP when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: API_TOKEN.
  • You want tools like GROUPS, TOOLS, search_engine.
Explore Brightdata MCP

W
Choose Webhound when

  • You need dedicated capabilities in the Search & Data Extraction domain.
Explore Webhound

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBrightdata MCP logoBrightdata MCP
W
Webhound
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal69/100 · Great37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthAPI key requiredNot declared
PricingFreemiumNot declared
Required env varsAPI_TOKENNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,685—
Directory activity 4 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools6Not listed

Tools & capabilities

Brightdata MCP tools 6

  • GROUPS
  • TOOLS
  • search_engine
  • scrape_as_markdown
  • ask_brightdata_assistant
  • custom

Webhound tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Brightdata MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "luminati-io-brightdata-mcp": {
      "command": "npx",
      "args": [
        "@brightdata/mcp"
      ],
      "env": {
        "API_TOKEN": "YOUR_API_TOKEN_HERE"
      }
    }
  }
}

Webhound

No confirmed install command for Webhound yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Brightdata MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. Webhound belongs to Search & Data Extraction and uses an install path we have not confirmed yet. Pick Brightdata MCP for search & data extraction work and Webhound for search & data extraction.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Webhound has no confirmed install command yet — follow its own setup instructions.

Brightdata MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Webhound has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add luminati-io-brightdata-mcp and webhound as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Brightdata MCP has a quality signal of 69/100 (Great) with 4 views, 0 installs and 2,685 GitHub stars. Webhound has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.