Google Search MCP Server

Created By
1999AZZARa year ago
MCP server proxy for Google Programmable Search Engine
Overview

what is MCP Server?

MCP Server is a simple server that acts as a proxy for the Google Programmable Search Engine, allowing users to fetch search results in JSON format.

how to use MCP Server?

To use MCP Server, set up the server by configuring your Google API key and Custom Search Engine ID, then run the server and make requests to the /search endpoint with your query.

key features of MCP Server?

  • Proxies requests to Google Custom Search API.
  • Returns search results as raw JSON.
  • Simple HTTP endpoint for easy integration.

use cases of MCP Server?

  1. Integrating Google search capabilities into applications.
  2. Fetching search results for data analysis.
  3. Building custom search interfaces for websites.

FAQ from MCP Server?

  • What do I need to run MCP Server?

You need Node.js, npm, a Google API key, and a Custom Search Engine ID.

  • How do I make a search request?

Use the endpoint /search?q=your+search+terms to get results.

  • What happens if I don't provide a query?

The server will return a 400 error if the q parameter is missing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
1999AZZAR
Star
0
Language
TypeScript
License
MIT 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