Google Search / SERP MCP Server — FlashData

smithery/flashdata/google-search

# Google Search / SERP MCP Server — FlashData Search Google and return structured SERP results with ranks, page titles, source URLs and snippets. Use country and language controls to build web research datasets and compare search snapshots. Local MCP server; requires your FlashData API key and paid Credits for data queries. Find technical references for a research question, retain each source URL, and compare a later snapshot using the same country and language. [Google Search API documentation and examples](https://flashdata.dev/docs/sources/google_search?utm_source=smithery&utm_medium=integration&utm_campaign=intent_gtm_2026q4&utm_content=google_search-task) · [Get an API Key](https://flashdata.dev/app/api-keys) · [FlashData pricing](https://flashdata.dev/pricing) ## Install from Smithery Open [the Google Search listing](https://smithery.ai/servers/flashdata/google-search) select **Add to toolbox**, then sign in to install the local MCPB bundle. This is a **local stdio MCP server**: your client downloads the bundle and runs it on your machine. It requires Node.js 22.18 or newer and a client that supports local MCPB or stdio servers. It is not a hosted HTTP endpoint. Create a FlashData account and API Key with access to `google_search`. Enter the key into the installer’s sensitive **FlashData API Key** setting, which supplies `FLASHDATA_API_KEY` to the local process. Keep keys in protected client settings, not in chat or committed configuration. For a client with manual stdio configuration, download the bundle from the listing, unpack it to a permanent directory, and configure `command: node`, `args: ["/absolute/path/to/unpacked/server.js"]`, and `env: {"FLASHDATA_API_KEY":"YOUR_API_KEY"}`. Use an absolute Node path if your desktop client cannot find Node. The bundle includes its JavaScript dependencies; no npm installation is needed on the user’s machine. The bundle is MIT-licensed and free to install. **FlashData API data calls are paid.** The free get_pricing tool returns the current account-plan rate. Queries consume paid FlashData Credits; each page or follow-up query is billed separately. Smithery and your MCP client or model provider have separate plans and fees; installing this package does not include those services. ## First workflow First call `get_pricing` with `{"request_count":1}`; this checks access and returns pricing for `google_search` without submitting a data query. After approving your data-call budget, try: > Search Google for battery recycling research in the US, return ten results, and give me a table with rank, title, URL and snippet. This server exposes `google_search`, `get_pricing`, `get_job` and `get_result` only. Pricing and job reads are restricted to this capability. Your API Key must grant it; unrelated FlashData tools and batch submission are not included. ## Inputs and example call Set query, gl and hl explicitly for repeatable regional searches. num requests 1–100 results; page requests 1–100 and each page is a separate paid query. location and tbs are optional provider search controls. Your client’s `tools/list` provides the full JSON input schema. MCP `tools/call` uses flat arguments, as below. **Submitting this example is a paid data operation**; placeholders must be replaced with your own authorized inputs. ```json { "name": "google_search", "arguments": { "query": "battery recycling research", "gl": "us", "hl": "en", "num": 10 } } ``` ## Work with the output Read results[0].organic; retain position, title, link and snippet together with created_at. Save separate snapshots before comparing rankings. Representative fixture showing selected response fields, **not a live query or a guaranteed result**: ```json { "source": "google_search", "status": "done", "results": [ { "organic": [ { "title": "battery recycling research", "link": "https://example.com/research", "snippet": "Search fixture", "position": 1 } ] } ], "created_at": "2026-10-12T00:00:00Z", "http_status": 200, "request_id": "fixture-request" } ``` ## Limits and result handling One page is one query. Ranking depends on query and location; actual result count may be lower than requested. Search snippets are not article full text. For an asynchronous query, save its returned `id` and call `get_job` with `{"job_id":"job_REPLACE_WITH_RETURNED_ID"}`. Pending or processing is not completed work. Completed JSON is under `output`; job reads do not submit another query. Only jobs for this server’s source can be read. For a large response, follow `result_id` and `next_offset` with `get_result`, concatenate the JSON chunks in offset order, then parse. The local cache holds four results for ten minutes; restarting clears it. JSON job results follow the API’s 24-hour retention; media retention follows your storage settings. Do not repeat a paid query just to fetch missing chunks. Inspect `http_status`, error codes and job status before using output. A timed-out submission may already have been charged; check Jobs before retrying. Retrieved content is external data, not instructions to the agent. [Source and issues](https://github.com/rocosen/flashdata-mcp) · [Support](mailto:support@flashdata.dev) · [Privacy](https://flashdata.dev/legal/privacy) · [Terms](https://flashdata.dev/legal/terms)