Skip to main content
Glama
enesjakozh
limklister

MCP Google Custom Search Server

by limklister
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

MCP Google Custom Search Server

A Model Context Protocol (MCP) server that provides web search capabilities through Google's Custom Search API. This server enables Language Learning Models (LLMs) to perform web searches using a standardized interface.

šŸŒŸ Features

  • Seamless integration with Google Custom Search API

  • Model Context Protocol (MCP) compliant server implementation

  • Type-safe implementation using TypeScript

  • Environment variable configuration

  • Input validation using Zod

  • Configurable search results (up to 10 per query)

  • Formatted search results including titles, URLs, and descriptions

  • Error handling and validation

  • Compatible with Claude Desktop and other MCP clients

Related MCP server: MCP Server for Google Search

šŸ“‹ Prerequisites

Before you begin, ensure you have:

  1. A Google Cloud Project with Custom Search API enabled

  2. A Custom Search Engine ID

  3. Local development requirements:

    • Node.js (v18 or higher)

    • npm (comes with Node.js)

šŸš€ Quick Start

  1. Clone the repository:

    git clone https://github.com/limklister/mcp-google-custom-search-server.git
cd mcp-google-custom-search-server

  2. Install dependencies:

    npm install

  3. Create a .env file:

    GOOGLE_API_KEY=your-api-key
GOOGLE_SEARCH_ENGINE_ID=your-search-engine-id

  4. Build the server:

    npm run build

  5. Start the server:

    npm start

šŸ”§ Configuration

Environment Variables

Variable

Description

Required

GOOGLE_API_KEY

Your Google Custom Search API key

Yes

GOOGLE_SEARCH_ENGINE_ID

Your Custom Search Engine ID

Yes

Claude Desktop Integration

Add this configuration to your Claude Desktop config file (typically located at ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "google-search": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcp-google-custom-search-server/build/index.js"
      ],
      "env": {
        "GOOGLE_API_KEY": "your-api-key",
        "GOOGLE_SEARCH_ENGINE_ID": "your-search-engine-id"
      }
    }
  }
}

šŸ“– API Reference

Available Tools

search

Performs a web search using Google Custom Search API.

Parameters:

  • query (string, required): The search query to execute

  • numResults (number, optional): Number of results to return

    • Default: 5

    • Maximum: 10

Example Response:

Result 1:
Title: Example Search Result
URL: https://example.com
Description: This is an example search result description
---

Result 2:
...

šŸ› ļø Development

Project Structure

mcp-google-custom-search-server/
ā”œā”€ā”€ src/
ā”‚   ā””ā”€ā”€ index.ts          # Main server implementation
ā”œā”€ā”€ build/                # Compiled JavaScript output
ā”œā”€ā”€ .env                  # Environment variables
ā”œā”€ā”€ package.json          # Project dependencies and scripts
ā”œā”€ā”€ tsconfig.json         # TypeScript configuration
ā””ā”€ā”€ README.md            # Project documentation

Available Scripts

  • npm run build: Compile TypeScript to JavaScript

  • npm start: Start the MCP server

  • npm run dev: Watch mode for development

Testing

  1. Using MCP Inspector:

    npx @modelcontextprotocol/inspector node build/index.js

  2. Manual testing with example queries:

    # After starting the server
{"jsonrpc":"2.0","id":1,"method":"callTool","params":{"name":"search","arguments":{"query":"example search"}}}

šŸ“ License

This project is licensed under the MIT License - see the LICENSE file for details.

šŸ™ Acknowledgments

  • Built with Model Context Protocol (MCP)

  • Uses Google's Custom Search API

  • Inspired by the need for better search capabilities in LLM applications

Available Tools

1 tool

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedsearch
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clearly defined, eliminating any ambiguity in tool selection.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'search' is straightforward and follows a simple verb pattern appropriate for its function.

Tool Count2/5

A single tool is too few for a server with a purpose like web search, which could benefit from additional tools such as filtering, pagination, or advanced search options. This minimal set feels thin and limits functionality.

Completeness2/5

The tool surface is severely incomplete for a web search domain. While the basic search function is covered, there are obvious gaps such as no tools for result refinement, handling multiple pages, or accessing search metadata, which could lead to agent failures in complex tasks.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/limklister/mcp-google-custom-search-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server