1. Conduid
  2. Developer Tools
  3. Google Custom Search
MCP server · Developer Tools

Google Custom Search

MCP Server for Google Search Integration

Unclaimed MIT last commit a year ago devtools
57Fair

Scored 12 days ago · breakdown

About Google Custom Search

Google Custom Search is an MCP server published by adenot in the Developer Tools category: mCP Server for Google Search Integration.

The repository has 71 stars and 23 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/adenot/mcp-google-search

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Google Custom Search

Powered by Claude · Grounded in docs

I know everything about Google Custom Search. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 5 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

0.3.10.3.1 · 24 Sep 2025Full Changelog: https://github.com/adenot/mcp-google-search/compare/0.3.0...0.3.1 What's Changed feat: add HTTPS_PROXY and HTTP_PROXY support by @Jonney in https://github.com/adenot/mcp-google-search/pull/6 New Contributors @Jonney made…
0.2.20.2.2 · 20 Jul 2025What's Changed seemingly required changes for tsc / package locking by @otakup0pe in https://github.com/adenot/mcp-google-search/pull/5 New Contributors @otakup0pe made their first contribution in…
0.2.10.2.1 · 9 Jun 2025What's Changed small superficial change to use console.log for info log by @rpivo in https://github.com/adenot/mcp-google-search/pull/3 New Contributors @rpivo made their first contribution in…
0.2.00.2.0 · 2 Feb 2025What's Changed Deployment: Dockerfile and Smithery config by @calclavia in https://github.com/adenot/mcp-google-search/pull/1 New Contributors @calclavia made their first contribution in https://github.com/adenot/mcp-google-search/pull/1…
0.1.20.1.2 · 1 Feb 2025Full Changelog: https://github.com/adenot/mcp-google-search/compare/0.1.1...0.1.2

README

mcp-google-server A MCP Server for Google Custom Search and Webpage Reading

smithery badge

A Model Context Protocol server that provides web search capabilities using Google Custom Search API and webpage content extraction functionality.

Setup

Getting Google API Key and Search Engine ID

  1. Create a Google Cloud Project:

    • Go to Google Cloud Console
    • Create a new project or select an existing one
    • Enable billing for your project
  2. Enable Custom Search API:

    • Go to API Library
    • Search for "Custom Search API"
    • Click "Enable"
  3. Get API Key:

    • Go to Credentials
    • Click "Create Credentials" > "API Key"
    • Copy your API key
    • (Optional) Restrict the API key to only Custom Search API
  4. Create Custom Search Engine:

    • Go to Programmable Search Engine
    • Enter the sites you want to search (use www.google.com for general web search)
    • Click "Create"
    • On the next page, click "Customize"
    • In the settings, enable "Search the entire web"
    • Copy your Search Engine ID (cx)

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Features

Search Tool

Perform web searches using Google Custom Search API:

  • Search the entire web or specific sites
  • Control number of results (1-10)
  • Get structured results with title, link, and snippet

Webpage Reader Tool

Extract content from any webpage:

  • Fetch and parse webpage content
  • Extract page title and main text
  • Clean content by removing scripts and styles
  • Return structured data with title, text, and URL

Installation

Installing via Smithery

To install Google Custom Search Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @adenot/mcp-google-search --client claude

To use with Claude Desktop, add the server config with your Google API credentials:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "google-search": {
      "command": "npx",
      "args": [
        "-y",
        "@adenot/mcp-google-search"
      ],
      "env": {
        "GOOGLE_API_KEY": "your-api-key-here",
        "GOOGLE_SEARCH_ENGINE_ID": "your-search-engine-id-here"
      }
    }
  }
}

Usage

Search Tool

{
  "name": "search",
  "arguments": {
    "query": "your search query",
    "num": 5  // optional, default is 5, max is 10
  }
}

Webpage Reader Tool

{
  "name": "read_webpage",
  "arguments": {
    "url": "https://example.com"
  }
}

Example response from webpage reader:

{
  "title": "Example Domain",
  "text": "Extracted and cleaned webpage content...",
  "url": "https://example.com"
}

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

README fetched from the repository 5 days ago. The original is authoritative.

Questions

About Google Custom Search

How do I install Google Custom Search?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Google Custom Search safe to use with an AI agent?

Its trust score is 57 out of 100 (fair). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Google Custom Search still maintained?

The last commit was a year ago and 6 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.