Integration

SerpData integration

SerpData returns Google results as JSON: web search (organic results, or the full page with People Also Ask, top stories, the local pack and related searches), Google Images, Videos, News, Shopping and Patents, autocomplete suggestions, Google Trends keyword comparisons and the Trending Now feed, and Google Maps places, with one place's details, reviews and photos. Every successful call costs one prepaid credit (failed calls are refunded) and each answer reports creditsRemaining. The web search's internal cookie_policy tuning knob is not exposed. Authentication is an API key, created on the SerpData dashboard's API keys page, sent in the x-api-key header.

Connect SerpData How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SerpData.Built from the 14 SerpData tools below, on the connection you add once.

What you can do with SerpData

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Place, 3 operations

get_placeGet placeGETAgents: ask firstReturns one Google Maps business by cid, placeId or fid (send one): address parts, coordinates, phone, website, categories, rating, review breakdown, opening hours and amenities. One credit per call.
search_placesSearch placesPOSTAgents: ask firstGoogle Maps local business results for q, near lat/lng or nationally when both are left out: position, title, address, coordinates, rating, category, phone, website and cid of each. limit 1 to 200 (default 20). One credit per call.
search_places_in_areaSearch places in areaGETAgents: ask firstSearches Google Maps for businesses matching query inside a map viewport centered on lat/lng (zoom sets its size). Returns cid, fid, name, address, rating, phone, website and photos of each, and hasMore. One credit per call.

Autocomplete suggestion, 1 operation

list_autocomplete_suggestionsList autocomplete suggestionsPOSTAgents: ask firstReturns the suggestions Google offers as the partial query q is typed, optionally for a country (gl) and language (hl). One credit per call.

Image, 1 operation

search_imagesSearch imagesPOSTAgents: ask firstGoogle Images results for q: title, page link, full image URL, thumbnail, source and sizes of each image. One credit per call.

News article, 1 operation

search_newsSearch newsPOSTAgents: ask firstGoogle News results for q: title, link, snippet, date, source and image of each article. One credit per call.

Patent, 1 operation

search_patentsSearch patentsPOSTAgents: ask firstGoogle Patents results for q, page by page (page starts at 1): title, snippet, key dates, inventor, assignee, publication number, PDF link and figures of each patent. One credit per call.

Place photo, 1 operation

list_place_photosList place photosGETAgents: ask firstReturns the photos of one Google Maps business (by cid, placeId or fid): image URL, hash, dimensions, source and categories of each, with totalCount and found. One credit per call.

Place review, 1 operation

list_place_reviewsList place reviewsGETAgents: ask firstReturns one page of a business's Google Maps reviews (by cid, placeId or fid), with nextPageToken for the next page. Reviews are personal data: reviewer name, id, photo and text. One credit per call.

Shopping result, 1 operation

search_shoppingSearch shoppingPOSTAgents: ask firstGoogle Shopping results for q: title, merchant, link, price, rating and product id of each offer. One credit per call.

Trend, 1 operation

get_trendsGet trendsPOSTAgents: ask firstGoogle Trends for one to five keywords (keyword mode): interest over time, interest by region, related queries and related topics, each as one item of results. Use get_trending_now for the Trending Now feed. One credit per call.

Trending search, 1 operation

get_trending_nowGet trending nowPOSTAgents: ask firstGoogle Trends Trending Now feed for one country: the searches trending over the last 4, 24, 48 or 168 hours, optionally in some categories, returned in results (section trendingNow). Use get_trends to compare keywords. One credit per call.

Video, 1 operation

search_videosSearch videosPOSTAgents: ask firstGoogle Videos results for q: title, link, snippet, duration, source, channel, date and thumbnail of each video. One credit per call.

Web result, 1 operation

search_webSearch webGETAgents: ask firstGoogle web search for q (10 results a page, start pages by 10 up to 90). mode=simple returns organic results; mode=rich adds People Also Ask, top stories, local pack, shopping, videos and related searches. One credit per call.

Use SerpData from Claude Code, Cursor or Codex

Connect SerpData in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SerpData operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SerpData

Create your workspace
Sign up free. Nothing to install.
Connect SerpData once
Add your SerpData connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.