Google Custom Search MCP Server

@fbettag

代码仓库

基本信息

分类

搜索

传输方式

stdio

作者

fbettag

提交者

Franz Bettag

关于 Google Custom Search MCP Server

暂无概览

#google-custom-search #api #python-server

Google Custom Search MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "google-search": {
      "command": "uv",
      "args": [
        "run",
        "path/to/your/clone/of/google-custom-search-mcp"
      ],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT_FILE": "/path/to/your/service-account-key.json",
        "GOOGLE_SEARCH_ENGINE_ID": "your-search-engine-id"
      }
    }
  }
}

Google Custom Search MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Google Custom Search MCP?

Google Custom Search MCP is an async Python MCP (Model Context Protocol) server that provides access to Google Custom Search API using service account authentication. It is designed for developers and AI assistants that need to perform Google Custom Search queries programmatically through the MCP protocol.

How to use Google Custom Search MCP?

Clone the repository, configure a Google Service Account and Custom Search Engine, then run uv run google-custom-search-mcp with the required environment variables GOOGLE_SERVICE_ACCOUNT_FILE or GOOGLE_SERVICE_ACCOUNT_BASE64 and GOOGLE_SEARCH_ENGINE_ID. The server supports STDIO mode (default) and HTTP mode (via --transport http). Docker and Helm deployments are available.

Key features of Google Custom Search MCP

Perform Google Custom Search queries with configurable result count
Service Account authentication (file path or base64)
Live integration tests against actual Google API
FastMCP Python SDK integration
Docker support with Alpine Linux image
UV compatibility for modern Python packaging

Use cases of Google Custom Search MCP

Building AI assistants that need real-time web search results
Enabling MCP clients to query Google Custom Search inside workflows
Integrating custom search into CI/CD pipelines with base64 auth
Deploying a custom search microservice on Kubernetes

常见问题

What is required to use Google Custom Search MCP?

You need a Google Cloud project with the Custom Search API enabled, a service account with a JSON key, and a Custom Search Engine ID. Environment variables authenticate the service account.

How does authentication work?

Authentication uses a Google Service Account, either via a file path (local development) or a base64-encoded JSON string (CI/CD). API keys are deprecated.

What are the API limits?

The Google Custom Search API provides 100 free search queries per day. Additional queries require billing setup. Service accounts have the

搜索分类下的更多 MCP 服务器

Gemini MCP

houtini-ai

Google Gemini MCP - Use Google's visual, video and chat capabilities in your AI Assistant. Uses MCP Apps to preview created images, landing pages, SVGs and video

Google Search MCP Server

HasData

Hosted Google Search / SERP MCP server from HasData, no Google Cloud project. Organic results, AI Overview, People Also Ask, AI Mode, news and shopping for Claude, Cursor and any MCP client.

Desearch

Desearch-ai

AI search, X search and web search for AI agents, plus page extraction and X data tools. Bring your own Desearch API key.

VarynForge

VarynForge is an SEO research SaaS that exposes its full workflow as MCP tools. Connect once from Claude Desktop, Claude Code, Cursor, Codex or any MCP host, then ask your agent to set up a project, hand it your article

UX Jobs

Search 4,000+ live UX, product-design and UX-research jobs from jobs.uxjobs.io — aggregated from 60+ applicant-tracking systems, re-verified against each employer, refreshed several times a day. Read-only, free, no sign-