MCP Google Custom Search Server

Created By
alexatnordneta year ago
An mcp server for searching against google custom search api
Overview

what is MCP Google Custom Search Server?

MCP Google Custom Search Server is a Model Context Protocol (MCP) compliant server that enables web search capabilities using Google's Custom Search API, specifically designed for integrating with Language Learning Models (LLMs).

how to use MCP Google Custom Search Server?

To use this server, clone the repository from GitHub, install the necessary dependencies, configure the environment variables with your Google API credentials, and run the server using Node.js.

key features of MCP Google Custom Search Server?

  • Seamless integration with Google Custom Search API
  • MCP compliant server implementation
  • Type-safe development environment with TypeScript
  • Configurable search results and error handling
  • Supports Claude Desktop and other MCP clients

use cases of MCP Google Custom Search Server?

  1. Enhancing search functionality in LLM applications.
  2. Providing developers with a standardized API for web search.
  3. Facilitating complex data retrieval tasks in research workflows.

FAQ from MCP Google Custom Search Server?

  • Do I need a Google Cloud Project to use this server?

Yes! You'll need to enable the Custom Search API and obtain API credentials from Google Cloud Console.

  • Can I configure the number of search results?

Yes! The server allows configuring up to 10 search results per query.

  • Is this server open-source?

Yes! This project is licensed under the MIT License and can be found on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
alexatnordnet
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
Tavily Mcp
@tavily-ai

JavaScript
a year ago