Skip to main content
Glama
Sign In
Google Maps Places Scraper MCP Server

Google Maps Places Scraper MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Google Maps Places Scraper MCP Server

No user-submitted related servers found.

    Related Servers

    • Local Business Lead Builder

      mambalabsdev
      A
      license
      A
      quality
      B
      maintenance
      Enables assembling local business prospect lists from Google Maps searches by category and place, returning one row per business with website, phone, address, coordinates, categories, rating, review count, and weekly hours. Supports filters for minimum rating, review count, website, and phone, plus URL and category-plus-location queries, deduplication across searches, and Clay-ready output via Apify.
      1
      71 npm
      MIT

    • gmapsscraper

      gmapsscraper
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to scrape Google Maps business data (names, addresses, phones, emails, websites, ratings, etc.) through natural language queries, with tools for synchronous and asynchronous scraping and credit checking.
      4
      40 npm
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool in the set, there is no possibility of misselection between tools. The tool's purpose (search places and resolve place IDs) is stated clearly enough that an agent will always know when to use it.

    Naming Consistency4/5

    The lone name search_google_maps_places follows a clean verb_noun snake_case convention and is descriptive. There is no second tool to demonstrate a consistent pattern across the set, so it cannot be judged a full 5.

    Tool Count3/5

    A single tool is thin for a scraping server; it bundles search, place-ID lookup, and full detail retrieval into one overloaded endpoint. It is workable but leaves no room for pagination control or separate detail retrieval.

    Completeness3/5

    The tool returns rich per-place data (phone, hours, ratings, attributes), which covers core read workflows, but the surface offers no pagination/bulk iteration, no separate reviews or photos retrieval, and no way to enumerate results beyond one query.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources