Headless Lead Scraping MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_MODEL | Yes | Model identifier, e.g., qwen3. | |
| LLM_API_KEY | Yes | API key for the LLM endpoint. Use a dummy value like 'ollama' or 'lm-studio' for local servers. | |
| LLM_BASE_URL | Yes | Base URL of the OpenAI-compatible API endpoint. | |
| LLM_PROVIDER | Yes | LLM provider identifier: ollama, lmstudio, openai, or any OpenAI-compatible provider. | |
| SEARCH_ENGINES | No | Comma-separated list of search engines to use, in priority order (e.g., googlemaps,yahoo,duckduckgo,bing,startpage). | |
| MAPS_SEARCH_URL | No | URL template for Google Maps search (e.g., https://www.google.com/maps/search/). | |
| MAPS_MAX_RESULTS | No | Maximum number of results to retrieve from Google Maps. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_webA | Search the live web across prioritized sources: googlemaps (browser-rendered local places) first, then web engines (yahoo, duckduckgo, bing) and related engines (startpage). No search API key or search provider SDK is required. |
| scrape_pageB | Fetch a public webpage in real time. Uses HTTP first and Playwright for JavaScript-rendered pages. |
| extract_leadsB | Extract supported lead fields from supplied public page content using the configured LLM. |
| find_leadsA | Find leads in priority order: Google Maps places first (browser-rendered, incl. phone/website/address), then live web search engines, then related search engines. Crawls relevant pages, extracts and verifies leads with the LLM, deduplicates, filters by requiredFields, and stores them locally. |
| list_stored_leadsB | Read leads stored locally by this MCP server. |
| filter_leadsA | Filter stored leads by keyword, required field presence, and minimum confidence. |
| export_leadsB | Export stored leads (optionally filtered) to a CSV or JSON file on disk. |
| clear_stored_leadsA | Delete all locally stored lead records. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/imshibaji/leads-scrapper-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server