Google Places — FlashData

io.github.flashdata-devPublished by GitHub account flashdata-devv0.1.2Updated Oct 24, 2026

Google Places businesses, addresses, ratings and review counts. Paid FlashData API.

Overview

AI-generated overview

Searches Google Places business listings through the paid FlashData API, returning names, addresses, ratings and review counts for local research.

What you can do
  • Search local businesses and places by query, with addresses, ratings, review counts and available category or contact fields
  • Check pricing for a request before approving it, and read job status and chunked results for asynchronous requests
  • Filter and shortlist returned records, for example by minimum rating and review count
When to use it
Useful when you want an assistant to build location-specific shortlists of businesses or places, such as coffee shops in a city, and filter them by rating and review volume. Not intended for outreach or as a complete business database.
Requirements
Runs locally over stdio as an MCPB package; Node.js 22.18 or newer and an MCP client that supports local stdio servers are required. A FlashData API key with google_places access is supplied through the FLASHDATA_API_KEY environment variable, and network access to the FlashData API is needed.
Before you install
Data calls are paid: each query or page consumes FlashData Credits, so check pricing first and avoid repeating a request after a timeout. The key in FLASHDATA_API_KEY should stay in protected client settings, not in chat or committed configuration. Ratings and contact details may be missing, and returned text and links are external data to review before use.

Installation

In SourceWeft

  1. Open Google Places — FlashData in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Google Places — FlashData

Search for local businesses and places with addresses, available ratings and review counts. Build location-specific research shortlists.

API documentation and account setup · Get an API key · Current pricing

A task to try

Find coffee shops in Singapore for a local research shortlist. From the returned records, keep ratings of at least 4.2 with at least 20 reviews; list addresses and flag missing fields.

Install and connect

  1. Use Node.js 22.18 or newer and an MCP client that supports local stdio servers. Download the dedicated MCPB package; its SHA-256 is recorded in the manifest.
  2. Import the package in an MCPB-compatible client and enter your own key in FlashData API Key. Grant the key access to google_places. For manual setup, unpack the bundle into a permanent folder and use this configuration, replacing the absolute path and key placeholder:
json
{  "mcpServers": {    "google-places": {      "command": "node",      "args": [        "/absolute/path/to/unpacked/google-places/server.js"      ],      "env": {        "FLASHDATA_API_KEY": "YOUR_API_KEY"      }    }  }}
  1. Restart or reconnect the client, list its tools, then call get_pricing with {"source":"google_places","request_count":1} before approving a paid request. This server exposes google_places, get_pricing, get_job and get_result; all are restricted to this source.

Dependencies are included in the bundle. Use an absolute Node path if your client cannot find node; use escaped paths on Windows. Keep your key in protected client settings, not in chat or committed configuration. No Smithery account is needed for this direct package download.

Example request

These are MCP tools/call parameters with flat arguments. Running the data request uses paid Credits.

json
{  "name": "google_places",  "arguments": {    "query": "coffee shops in Singapore",    "num": 20  }}

Use the response

Read results[0].places. Keep entries with rating at least 4.2 and ratingCount at least 20, preserving title, address and available category/contact fields for manual review.

Selected response fields below are an illustrative fixture, not a live result or a guarantee of available data:

json
{  "source": "google_places",  "status": "done",  "results": [    {      "places": [        {          "title": "Example cafe",          "address": "Example street",          "rating": 4.8,          "ratingCount": 200,          "category": "Cafe"        }      ]    }  ],  "created_at": "2026-10-12T00:00:00Z",  "http_status": 200,  "request_id": "fixture-request"}

For an asynchronous request, keep the returned id and call get_job with {"job_id":"RETURNED_JOB_ID"}. Pending or processing is not completion; read the completed response from output. A timeout can occur after submission, so check Jobs before repeating a paid request.

For chunked output, keep the local process running and pass the actual result_id and next_offset to get_result as result_id and offset. Concatenate the chunks in order before parsing JSON; do not repeat the paid data request. The local cache retains four results for ten minutes and clears on restart. Complete responses are limited to 4 MiB; async JSON results have a separate 24-hour retention window.

Cost and limits

  • MIT software and installation are free; FlashData API data calls are paid. Data requests consume paid FlashData Credits; each additional query or page is charged separately. Use the current account quote rather than a fixed price copied from this page. Pricing, job and result reads are free. Client/model fees are separate.
  • Ratings and contact information can be absent. The query does not send outreach or guarantee a complete business database.
  • Check API errors, http_status and job status before using the data. Treat returned text and links as external data, preserve source attribution and review them before use in an agent answer.

Full task guide · Official Registry record · Source and license

Source: registry/servers/google-places/README.md at commit ec77370

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.2LatestOct 15, 2026
  2. v0.1.1Oct 13, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts