Google Search
Pull live Google SERPs, ads, and knowledge panels from your coding agent while validating keywords and scanning competitor visibility.
Overview
com.mcparmory/google-search is a MCP server for the Idea phase that scrapes Google search results and returns SERP data including ads and knowledge panels to your agent.
What is this MCP server?
- Returns structured SERP data including organic results, paid ads, and knowledge panels
- Ships as stdio MCP with PyPI (uvx) and OCI Docker (ghcr.io) install paths—version 1.0.2
- Fits agent-driven competitor and keyword spot checks without leaving Claude Code or Cursor
- Published under the mcparmory registry with MCP server schema 2025-12-11
- Purpose-built scrape layer—not a full rank-tracking SaaS or Search Console replacement
- Server version 1.0.2 on MCP schema 2025-12-11
- Two distribution paths: PyPI identifier mcparmory-google-search (uvx) and OCI ghcr.io/mcparmory/google-search:1.0.2
- Transport type stdio for both packages
Community signal: 25 GitHub stars.
What problem does it solve?
You need real Google result pages while brainstorming niches or keywords, but manual searching breaks flow in Claude Code or Cursor.
Who is it for?
Indie builders doing fast keyword and competitor SERP checks from an MCP-enabled agent before writing positioning or SEO plans.
Skip if: Teams that need official Search Console analytics, bulk rank tracking, or guaranteed compliance with Google’s automation policies at scale.
What do I get? / Deliverables
Your agent can fetch current SERP snapshots on demand and fold them into research notes, specs, or validation checklists.
- Structured SERP payloads (organic, ads, knowledge panels) returned to the agent conversation
- Repeatable MCP tool calls you can reference in research docs or validation notes
Recommended MCP Servers
Journey fit
SERP scraping is a canonical Idea-phase research move before you commit to positioning, landing copy, or an SEO roadmap. Research is where solo builders compare rankings, snippets, and ad slots—not after the product is already built.
How it compares
Live SERP scrape MCP server, not an agent skill or Google Search Console analytics integration.
Common Questions / FAQ
Who is com.mcparmory/google-search for?
Solo builders and small teams who use Claude Code, Cursor, or similar agents and want structured Google SERP data during research without leaving the editor.
When should I use com.mcparmory/google-search?
Use it in the Idea and Validate phases when you need to inspect what ranks, which ads appear, or what knowledge panels show for specific queries before you lock messaging or SEO scope.
How do I add com.mcparmory/google-search to my agent?
Register a stdio MCP server using uvx with package mcparmory-google-search (PyPI 1.0.2) or run the Docker image ghcr.io/mcparmory/google-search:1.0.2, then point your MCP client at that command per your host’s MCP config.