
Google Ai Overview
io.github.johnisanerdPublished by GitHub account johnisanerdv1.1.0Updated Nov 8, 2026
Google AI Overview answers and their cited sources. Paid, on Apify's hosted MCP.
Overview
Fetches Google's AI Overview answer and its cited sources for search queries as structured JSON, via Apify's hosted MCP endpoint.
- What you can do
- Retrieve Google AI Overview answers for a single query or a batch of queries, one result row per query.
- Get the answer as ordered text blocks plus cited references with title, link, snippet and source name.
- Resolve Google's deferred, token-based generation automatically so a full answer comes back in one run.
- Target results by country, language and optional location.
- Report whether an overview was present, a note when none was shown, and how many retrievals were used.
- When to use it
- Useful when you want an assistant to pull Google's AI-generated answer and its citations into research, reporting, content or GEO/AEO monitoring workflows without parsing HTML. Also handy for batch lookups across many queries.
- Requirements
- Remote MCP endpoint at mcp.apify.com, preloaded with this Actor. An Apify account is required; authenticate with OAuth in the browser or with an Apify API token sent as an Authorization Bearer header. Usage is paid per retrieval.
Installation
In SourceWeft
- Open Google Ai Overview in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.johnisanerd%2Fgoogle-ai-overview/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"google-ai-overview": {
"type": "http",
"url": "https://mcp.apify.com/?tools=johnvc/Google-AI-Overview-API"
}
}
}README
🔎 Google AI Overview API: Get Google's AI answer and its sources as JSON
The most efficient, reliable, and developer-friendly way to use the Google AI Overview API.
Actor page: apify.com/johnvc/Google-AI-Overview-API Input schema: apify.com/johnvc/Google-AI-Overview-API/input-schema
Send any search query and get back Google's AI Overview, the AI-generated answer that appears at the top of Google's results, as structured JSON: the answer text blocks plus the sources it cites (title, link, snippet, and source name). When Google defers generation and returns only a short-lived token, this API resolves the full answer for you automatically, so you always get clean, ready-to-use data.
Video Walkthrough
Quick Start
Prerequisites
- Python 3.11 or higher
- An Apify account and API key (get a free key here)
-
Clone the repository
-
Install dependencies with UV
-
Configure your API key
-
Run the example
Alternative: set the API key directly
Why Use This Google AI Overview API?
Just the answer, structured. You get the AI Overview content and its cited sources as clean JSON, ready to drop into a database, a report, or an LLM pipeline. No HTML parsing.
It handles Google's deferral for you. Google sometimes returns the AI Overview immediately and sometimes defers it behind a short-lived token. This API resolves that follow-up automatically in a single run, so you never have to manage tokens that expire in under a minute.
One query or many. Pass a single query or a queries list. You get one result row per query, which makes batch lookups and GEO/AEO monitoring straightforward.
Pay only for what you fetch. Pricing is per retrieval: one retrieval for a standard inline answer, two only when Google defers and a follow-up is required. The output tells you exactly how many were used.
Country and language targeting. Choose the country (gl) and language (hl), or narrow to a specific location.
MCP-ready. Load it as a tool in Claude Cowork, Claude Code, Claude on the web, and Cursor (see below) and ask for an AI Overview in plain language.
Features
Core Capabilities
- Returns the AI Overview answer as ordered
text_blocks(paragraphs, headings, lists) - Returns the cited
referencesfor each answer (title, link, snippet, source) - Automatic resolution of Google's deferred (token-based) generation
- Single-query and batch (
queries) input, one row per query - Country, language, and location targeting
Data Quality
- Clean, typed JSON output, one row per query, with a stable
result_typefield - A clear
ai_overview_presentflag and anotewhen Google shows no overview - Transparent
retrievals_usedcount so cost is never a surprise
Usage Examples
Basic Example
Advanced Example
Input Parameters
At least one of query or queries is required.
Output Format
One row per query. Each item has a result_type of ai_overview or error. The answer text and sources below are illustrative; your run returns the live AI Overview content and its real citations.
When Google does not show an AI Overview for a query, the row comes back with "ai_overview_present": false and a short note explaining why.
Use as an MCP tool
You can load the Google AI Overview API as an MCP tool so assistants call it for you. The MCP server URL preloads just this one Actor:
Authenticate with OAuth in the browser when offered, or with your Apify API token (the same APIFY_API_TOKEN used by the Python example). Get a token at https://console.apify.com/settings/integrations and a free Apify account at https://apify.com?fpr=9n7kx3 .
Install in Claude Cowork Desktop
[Install in Claude Cowork Desktop]
Cowork is the desktop app's automation mode. To give it the Google AI Overview API as a tool, add the Apify MCP server as a connector.
- Open the Claude desktop app and go to Settings → Connectors (or Settings → Developer → Edit Config to edit
claude_desktop_config.jsondirectly).- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Add the Apify MCP server, preloaded with only this Actor:
- Restart the app. When Cowork first calls the tool, complete the OAuth prompt in your browser, or add your Apify API token in the connector settings to skip OAuth.
- In a Cowork chat, confirm the tool is available and ask it to run the Google AI Overview API.
Download the desktop app and start a free trial: https://claude.ai/referral/uIlpa7nPLg More help: https://docs.apify.com/platform/integrations/claude-desktop
Install in Claude Code
Claude Code is the command-line tool. Add the Actor's MCP server with one command:
To use a token instead of browser OAuth:
Then verify with claude mcp list, or run /mcp inside a session. Ask Claude Code to call the Google AI Overview API.
Try Claude Code free: https://claude.ai/referral/uIlpa7nPLg Claude Code MCP docs: https://code.claude.com/docs/en/mcp
Install in Claude (website)
On claude.ai you add Apify as a connector, then enable just this Actor's tool.
- Go to Settings → Connectors → Browse connectors and search for Apify MCP server. Install it (enable or update if prompted).
- When connecting, authenticate with your Apify API token, and enable the tool
johnvc/Google-AI-Overview-API. - In any chat, open + → Connectors and turn on Apify.
- Alternatively, choose Add custom connector and paste the full MCP URL
https://mcp.apify.com/?tools=actors,docs,johnvc/Google-AI-Overview-API, using OAuth when prompted. - Ask Claude to run the Google AI Overview API.
Open Claude on the web: https://claude.ai/referral/uIlpa7nPLg
Install in Cursor
Cursor reads MCP servers from a project file at .cursor/mcp.json.
- In your project, create
.cursor/mcp.json:
- If you prefer token auth over browser OAuth, add a header:
- Open Cursor → Settings → MCP and confirm the apify server is connected (green dot).
- In Composer or Chat, ask Cursor to call the Google AI Overview API.
New to Cursor? Get it here: https://cursor.com/referral?code=XQP4VBLI3NNX
Install in ChatGPT
ChatGPT connects to the Apify MCP server through Developer mode (available on ChatGPT Pro, Plus, Business, Enterprise, and Education plans).
- Click your profile icon, then go to Settings > Apps. If you do not see a Create app button, open Advanced settings and enable Developer mode.
- Click Create app and fill out the form:
- Name: Apify
- MCP Server URL:
https://mcp.apify.com/?tools=actors,docs,johnvc/Google-AI-Overview-API - Authentication: OAuth
- Click Create and authorize the connection with Apify.
- To use the app in a conversation, click + in the chat, choose Developer mode, and select Apify.
More help: https://docs.apify.com/platform/integrations/mcp
Use the Google AI Overview API to power GEO/AEO monitoring, research, and content workflows with reliable, structured results.
🤖 Ask an AI assistant about this Actor
Open a ready-to-send prompt about the Google AI Overview API in the AI of your choice:
- 💬 ChatGPT
- 🧠 Claude
- 🔍 Perplexity
- 🅒 Copilot
Last Updated: 2026.10.27
Source: README.md at commit c351a62
Tools
0Version history
2- v1.1.0LatestNov 7, 2026
- v1.0.0Sep 16, 2026
Score
83% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.