Expose Bright Data web search tools to Claude, Cursor, and other MCP clients

Description

Quick overview
This workflow exposes a bearer-protected MCP server that gives Claude, Cursor, or other MCP clients web search and page-reading tools backed by Bright Data (Google search, Google AI Overview, People Also Ask questions, Bing search, Bing news, and a markdown page reader).

How it works
Publishes an MCP server endpoint protected with bearer authentication.
Sends Google search requests to Bright Data and returns only trimmed organic result fields (rank, title, link, description, source).
Fetches Google’s AI Overview for a query via Bright Data and returns the overview text plus cited references.
Retrieves Google “People Also Ask” related questions via Bright Data and returns the ranked question list.
Runs Bing web search and Bing News search via Bright Data and returns trimmed result fields with direct links.
Reads any given URL through Bright Data’s Web Unlocker and returns the page content as markdown.
Optionally lets you test the MCP tools in n8n Chat using an OpenAI Chat Model-powered agent that calls the same MCP server.

Setup
Create a Bright Data API key and add it to an HTTP Header Auth credential (Authorization: Bearer YOUR_KEY) used by all six Bright Data tool requests.
Ensure your Bright Data zones exist and match the workflow settings (serp_api1 for searches and web_unlocker1 for page reads), or update the zone values in the tool configurations.
Add a Bearer Auth credential to the MCP Server Trigger and configure the same token in your MCP client.
If you use the in-workflow test agent, add OpenAI credentials and update the MCP client endpoint URL (defaults to http://localhost:5678/mcp/bright-data-web) to match where n8n is reachable.