Google Search MCP Server

Created By
mixelpixxa year ago
An MCP (Model Context Protocol) server that provides Google search capabilities and webpage content analysis tools. This server enables AI models to perform Google searches and analyze webpage content programmatically.
Overview

What is Google Search MCP Server?

Google Search MCP Server is an MCP (Model Context Protocol) server that provides Google search capabilities and webpage content analysis tools, enabling AI models to perform Google searches and analyze webpage content programmatically.

How to use Google Search MCP Server?

To use the server, clone the repository, install the necessary dependencies, configure your Google API credentials, and run the server using the provided scripts.

Key features of Google Search MCP Server?

  • Advanced Google Search with filtering options (date, language, country, safe search)
  • Detailed webpage content extraction and analysis
  • Batch webpage analysis for comparing multiple sources
  • Environment variable support for API credentials
  • Comprehensive error handling and user feedback
  • MCP-compliant interface for seamless integration with AI assistants

Use cases of Google Search MCP Server?

  1. Performing advanced searches for specific topics with filters.
  2. Extracting and analyzing content from webpages for research.
  3. Comparing information from multiple sources for comprehensive insights.

FAQ from Google Search MCP Server?

  • What are the prerequisites for using the server?

You need Node.js, Python, a Google Cloud Platform account, a Custom Search Engine ID, and a Google API Key.

  • Is there a way to run the server on different platforms?

Yes, the server can be run on Windows and other platforms with the appropriate configurations.

  • How does the error handling work?

The server provides detailed error messages for missing credentials, failed requests, and network issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mixelpixx
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago