Integration

Zenserp integration

Zenserp scrapes live search engine result pages and returns them as JSON. An agent can run Google web searches (with optional AI Overview or Google Jobs results), Google Image, News, Maps and Shopping searches, Google reverse image searches, YouTube, Bing and Yandex searches, read a Google Shopping product page with every seller offer, search Google Hotels and Google Flights, and check the requests left on the key. A successful live search uses one request of the plan (three when an AI Overview is returned); failed requests and answers served from the cache are not charged. Not exposed: Google video and Trends searches, DuckDuckGo, the answer-engine (ChatGPT, Perplexity) monitoring, raw HTML or Markdown output, the asynchronous batch endpoints and the location, country, language and engine lists. Authentication is a Zenserp API key sent in the apikey header.

Connect Zenserp How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Zenserp

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.

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

Flight, 1 operation

google_flights_searchGoogle flights searchGETSearches Google Flights for a route given as origin and destination airport codes with dates (or as a free-text q, which carries no dates) and returns flights with airline, departure and arrival, duration, stops, price and CO2 emissions.

Hotel, 1 operation

google_hotels_searchGoogle hotels searchGETSearches Google Hotels for an area, for example hotels in vienna, and returns hotels with nightly price, rating, review count, class and amenities, for optional dates and guests. The answer to a query naming one property is not documented.

Search, 1 operation

google_searchGoogle searchGETRuns a Google web search and returns the parsed result page: organic results, related searches, pagination and, when Google shows them, ads, local results, answer boxes, an AI Overview or Google Jobs results.

Search bing, 1 operation

bing_searchBing searchGETRuns a Bing web search and returns the parsed result page: organic results, related searches, people-also-ask questions, images, videos and pagination.

Search image url, 1 operation

google_reverse_image_searchGoogle reverse image searchGETRuns a Google reverse image search for an image URL and returns pages showing the image, visually similar images and organic results.

Search isch, 1 operation

google_image_searchGoogle image searchGETRuns a Google Image search (tbm=isch) and returns up to 100 image results per page with their thumbnail, image URL, title, page and source.

Search lcl, 1 operation

google_maps_searchGoogle maps searchGETSearches Google Maps local results (tbm=lcl), for example shops or restaurants near a location, with name, address, rating, review count, type, coordinates and place id.

Search nw, 1 operation

google_news_searchGoogle news searchGETRuns a Google News search (tbm=nws) and returns the news results with title, link, source, date, description and thumbnail.

Search shop, 1 operation

google_shopping_searchGoogle shopping searchGETRuns a Google Shopping search (tbm=shop) and returns product offers with title, price, seller, rating and product id; pass the product id to get_shopping_product.

Search yandex, 1 operation

yandex_searchYandex searchGETRuns a Yandex web search and returns the organic results (URL, title, snippet).

Search youtube, 1 operation

youtube_searchYoutube searchGETSearches YouTube and returns the video results (title, URL, description, length, publish date, channel), channel and movie results and similar searches.

Shopping, 1 operation

get_shopping_productGet shopping productGETReturns a Google Shopping product page: title, description, image, specifications, reviews and every seller offer with item, shipping, tax and total price.

Status, 1 operation

get_statusGet statusGETReturns how many requests the API key has left in the current billing period.

Use Zenserp from Claude Code, Cursor or Codex

Connect Zenserp in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Zenserp 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 Zenserp

Create your workspace
Sign up free. Nothing to install.
Connect Zenserp once
Add your Zenserp 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.