Headless Lead Scraping MCP Server
MCP server for real-time public-web lead research without search API keys, using Google Maps and web search engines with LLM-based extraction, crawling, and local lead storage/export.
README
Headless Lead Scraping MCP Server v0.4.0
A UI-free MCP server for real-time public-web lead research with no search API provider, no Tavily key, and no hosted scraping service.
What it does
- Searches Google Maps first (browser-rendered) for local places — returns name, address, phone, and official website.
- Then searches web search engines (Yahoo, DuckDuckGo, Bing) directly at request time, with no search API key.
- Then searches related search engines (Startpage, browser-rendered) as an extra fallback source.
- Fetches target websites directly over HTTP.
- Falls back to headless Chromium/Playwright for JavaScript-rendered pages.
- Crawls relevant internal contact/about/team/social pages.
- Uses the configured LLM through the Vercel AI SDK for structured extraction and verification.
- Deduplicates results and filters by required fields.
- Stores leads locally in
data/leads.jsonl. - Filters stored leads and exports them as CSV or JSON files.
- Exposes everything as MCP tools over stdio.
Data-source priority
Sources are tried in order until enough results are found:
- Google Maps (
googlemaps) — browser-renderedgoogle.com/maps/search/; best for local businesses/product companies (name, address, phone, website, rating). - Web search engines — Yahoo, DuckDuckGo, Bing (
yahoo,duckduckgo,bing). - Related search engines — Startpage (
startpage, browser-rendered) for additional coverage.
The order is configurable via SEARCH_ENGINES (comma-separated). Maps-related settings: MAPS_SEARCH_URL, MAPS_MAX_RESULTS.
No external data API
There is no Tavily, Bing Search API, Google Search API, SerpAPI, Apify, Bright Data, or hosted scraper in this version.
The server performs search by requesting normal public search-result webpages and Google Maps search pages directly. Engines that respond with a CAPTCHA or bot-challenge page are skipped automatically. This means there is no API account or API key for search, but a public search website is still necessarily involved: the open Internet has no universal built-in index that a standalone program can query without using some indexed search source or already-known URLs.
If a search website blocks automated requests, the server cannot and does not bypass CAPTCHA, login, paywalls, robots directives, rate limits, or access controls.
LLM
The only required AI dependency is your LLM endpoint. The server supports OpenAI-compatible endpoints, including:
- Ollama
- LM Studio
- OpenAI
- other OpenAI-compatible local/self-hosted endpoints
For maximum independence, use Ollama or LM Studio locally.
Playwright
Playwright is the browser engine, not a lead-data provider. It is used only when a normal HTTP fetch cannot obtain the rendered page content or when browser rendering is explicitly requested.
Install Chromium:
npm install
npx playwright install chromium
Install
cp .env.example .env
npm install
npx playwright install chromium
npm run build
npm start
For development:
npm run dev
Ollama
ollama pull qwen3
.env:
LLM_PROVIDER=ollama
LLM_MODEL=qwen3
LLM_BASE_URL=http://127.0.0.1:11434/v1
LLM_API_KEY=ollama
LM Studio
Start a local OpenAI-compatible server in LM Studio and set:
LLM_PROVIDER=lmstudio
LLM_MODEL=YOUR_LOADED_MODEL_ID
LLM_BASE_URL=http://127.0.0.1:1234/v1
LLM_API_KEY=lm-studio
MCP tools
search_web— live web search in priority order (Google Maps, then web engines, then related engines); optionalenginesparam.scrape_page— HTTP fetch + Playwright fallback.extract_leads— LLM extraction from supplied page content.find_leads— Google Maps place discovery first, then web + related engine search; crawls, extracts, verifies, deduplicates, filters byrequiredFields, stores.list_stored_leads— read locally stored records.filter_leads— filter stored leads by keyword, field presence, and minimum confidence.export_leads— write stored leads (optionally filtered) to a CSV or JSON file on disk.clear_stored_leads— clear local records.
Example
{
"query": "software development companies",
"location": "California, USA",
"limit": 25,
"requiredFields": ["name", "website", "email"],
"maxSearchQueries": 8
}
requiredFields filters out any lead missing all of the listed fields. Default is ["name"].
Export example:
{
"format": "csv",
"hasEmail": true,
"minConfidence": "medium",
"filename": "california-leads"
}
This writes data/california-leads.csv (or .json for format: "json") and returns the file path and row count.
Stored data
Default:
data/leads.jsonl
No hosted database is required. The file is local to the MCP server process.
Important limitation
A truly provider-free program cannot discover arbitrary Internet resources from nothing: search requires an index or known URLs. This project removes search APIs and hosted scraping providers and performs live search-page retrieval itself. It does not pretend that the Internet has a universal local index.
Only publicly accessible information is collected. The server does not bypass authentication, CAPTCHA, paywalls, robots/access controls, or other security mechanisms.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.