MCP Gemini Grounded Search MCP Server

MCP Gemini Grounded Search is a Go-based MCP server that provides grounded search functionality using Google's Gemini API. MCP clients such as Claude Desktop and Claude Code can perform real-time web searches and retrieve up-to-date. The mcp gemini grounded search mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

• MCP Compliance — JSON-RPC based interface for tool execution per the MCP specification
• Grounded Search — Gemini API generates answers with source attributions
• Two Transport Modes — stdio (for Claude Desktop / Claude Code) and Streamable HTTP
• Flexible Configuration — config file, environment variables, or command-line flags

Its toolset

Everything the assistant can do here goes through one of these:

• search — Performs a web search using the Gemini API and returns a grounded answer with sources

Configuration

You will need 5 environment variables: GEMINI_MODEL_NAME, GEMINI_THINKING_LEVEL, GEMINI_API_KEY, HTTP_AUTH_TOKEN, HTTP_ENDPOINT_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Docker (recommended) For local development: - Go 1.24 or later - Gemini API key

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at cnosuke/mcp-gemini-grounded-search on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Gemini Grounded Search's toolset — search — is a fair guide to whether it matches your workflow. It is maintained by cnosuke; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp gemini grounded search mcp server does with a few real requests.