Local Business Lead Builder MCP Server
Related Servers
Alternatives to Local Business Lead Builder MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables turning Google Maps queries into structured lead lists, extracting business names, phone numbers, websites, and reviews with asynchronous job control.-
- FlicenseNot gradedqualityDmaintenanceProvides tools to search and get details of places via Apify's Google Maps Scraper.-
- AlicenseNot gradedqualityDmaintenanceEnables searching Google Local for businesses by keyword and location, returning details like name, address, phone, hours, ratings, and more. Useful for lead generation, local SEO, and market analysis.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to scrape Google Maps business leads, including contact details, emails, websites, and social profiles, and export them as CSV or XLSX.621 npmMIT
- AlicenseNot gradedqualityBmaintenanceStandalone MCP server exposing Google Maps business search (name, address, phone, rating, hours, GPS coordinates) as a tool, backed by an Apify Actor. Free hosted endpoint included.159 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and scrape Google Maps places data (name, rating, address, etc.) directly without an API key.1-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between competing tools. Its purpose (building a local business lead list from Google Maps queries) is unmistakable from the name and description.
A single snake_case verb_noun-style name (build_local_business_leads) that clearly states the action and the resource. With one tool there is no convention mixing, and the name is descriptive rather than vague.
One tool is defensible because it wraps a single batch workflow (search, filter, and bill in one call), but it is still thin for the domain. There is no separation between starting a run, checking run status, and retrieving results, which forces everything through one opaque operation.
The core operation is richly specified, covering queries, filters, deduplication, output fields, and pricing. However, the description mentions failed runs returned with a run ID yet provides no tool to fetch or retry that run, and there is no way to list prior results or datasets, leaving dead ends.