MCP · Google (Programmable / Custom Search)

Google (Programmable / Custom Search) MCP server: add Google (Programmable / Custom Search) search to Claude, Cursor & Cline

Add Google (Programmable / Custom Search) web search to any MCP client in 30 seconds. GroundRoute wraps Google (Programmable / Custom Search) (and 5 other engines) behind one MCP server — pin Google (Programmable / Custom Search) as the default or let the router pick the cheapest engine per query class. Google (Programmable / Custom Search) pricing: ~$5 / 1k (free 100/day).

Install — Claude Desktop, Cursor, Cline

Add this to your MCP config. GROUNDROUTE_DEFAULT_ENGINE pins Google (Programmable / Custom Search) as the preferred engine; the router still switches to a cheaper engine when quality is equivalent.

{
  "mcpServers": {
    "groundroute": {
      "command": "npx",
      "args": ["-y", "@groundroute/mcp"],
      "env": {
        "GROUNDROUTE_API_KEY": "your-key",
        "GROUNDROUTE_DEFAULT_ENGINE": "google"
      }
    }
  }
}

Get your API key at groundroute.ai/signup. BYOK: bring your own Google (Programmable / Custom Search) key and route on it for free.

Google (Programmable / Custom Search) pricing & limits

Google (Programmable / Custom Search)Details
List price~$5 / 1k (free 100/day) (verify)
Free tier100 queries/day (verify)
Best forraw web breadth
Honest weaknessstrict quotas; not agent-shaped

Why route Google (Programmable / Custom Search) through GroundRoute?

GroundRoute routes each query to the cheapest engine that clears the quality bar, and caches the repeats. You keep ~half the cache savings, we keep the other half — so you're never worse off than calling Google (Programmable / Custom Search) direct. Prefer your own accounts? BYOK: bring your Google (Programmable / Custom Search) key and route on it, with failover, spend caps, and one schema across every engine.

In practice: GroundRoute sends the queries Google (Programmable / Custom Search) is best at to Google (Programmable / Custom Search), and routes simpler lookups to cheaper engines that clear the quality bar — so you get Google (Programmable / Custom Search) quality where it matters without paying Google (Programmable / Custom Search) prices on every call.

Related

FAQ

What is the Google (Programmable / Custom Search) MCP server?
An MCP server lets AI clients like Claude Desktop and Cursor call Google (Programmable / Custom Search) search as a tool. GroundRoute wraps Google (Programmable / Custom Search) (and 5 other engines) behind one MCP endpoint — you can pin Google (Programmable / Custom Search) as the default or let the router choose the cheapest engine per query.
How do I add Google (Programmable / Custom Search) search to Claude Desktop?
Add the GroundRoute server block to claude_desktop_config.json (see above) and set GROUNDROUTE_DEFAULT_ENGINE to "google". Restart Claude Desktop. The search tool appears automatically.
Is Google (Programmable / Custom Search) MCP free?
BYOK is free — bring your own Google (Programmable / Custom Search) key. The managed tier has a free credit on signup. With GroundRoute you keep ~half the cache savings, so you never pay more than hitting Google (Programmable / Custom Search) direct.
Google (Programmable / Custom Search) vs multi-engine routing — which is better?
Google (Programmable / Custom Search) is raw web breadth. For queries in those classes it's often the right call. For other query types (plain web/news lookups), cheaper engines match quality at a fraction of the cost. Multi-engine routing lets you get Google (Programmable / Custom Search) where it matters without paying Google (Programmable / Custom Search) prices on every call.
Add Google (Programmable / Custom Search) search to your AI agent:Get an API keyTry it in the playground →

Pricing reflects public data as of 2026 — verify with Google (Programmable / Custom Search).