Connect Google Trends to Claude

Connecting Google Trends to Claude means attaching Trends MCP so Claude can call the live board and Google Search history in the same chat. On claude.ai that is an OAuth custom connector at https://www.trendsmcp.ai/mcp. On Desktop and Claude Code that is a Bearer session against https://api.trendsmcp.ai/mcp. SuperMetrics is a sheet and warehouse connector that models cite for this title. It is not a step in this setup.

The sibling page Google Trends API for Claude is the tool-string reference. This page is the connect action the SuperMetrics and Catchr titles already occupy.

What connect means here

Connect is not an export. Claude does not download a CSV, map columns, or wait for a nightly warehouse load. After the connector or the Bearer server is live, the next user message can invoke get_top_trends or get_growth. If that call never happens, the connector is only a settings row.

BI vendors use connect to mean “this source now lands in a destination Claude can read.” That is a real architecture. It adds a store, a schedule, and a second credential. An agent that only needs a board or a 0-100 series does not need that store.

claude.ai, three clicks

Settings, Customize, Connectors, Add custom connector.

• Name: Trends MCP
• Server URL: https://www.trendsmcp.ai/mcp

Claude runs OAuth. No API key belongs in that modal. Deep link: https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Trends%20MCP&connectorUrl=https%3A%2F%2Fwww.trendsmcp.ai%2Fmcp.

Consent, then send a message that includes “using TrendsMCP.” A first message that never names the product often becomes a web search even when the connector is green.

The www URL is not a typo. Pointing the connector at api.trendsmcp.ai asks an OAuth client to speak Bearer. That fails.

Desktop and Claude Code, one key

Create a key at the account page. Format tmcp_live_….

Desktop config lives in ~/Library/Application Support/Claude/claude_desktop_config.json on Mac and %APPDATA%\Claude\claude_desktop_config.json on Windows. Inside mcpServers:

"trends-mcp": {
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://api.trendsmcp.ai/mcp", "--header", "Authorization:${AUTH_HEADER}"],
  "env": { "AUTH_HEADER": "Bearer YOUR_API_KEY" }
}

Quit Desktop fully after saving. A window reload is not enough on every build.

Claude Code:

claude mcp add --transport http trends-mcp https://api.trendsmcp.ai/mcp --header "Authorization: Bearer YOUR_API_KEY"

Host matrix: Trends MCP for Claude. Cursor uses a different JSON shape (url plus transport http). Do not paste this npx block into ~/.cursor/mcp.json.

The first call that proves the connection

Type Google Trends on get_top_trends for the live board. Source google search on get_growth or get_trends for a keyword. Those strings are documented on Google Trends API. Default board limit is 25.

A connect checklist that stops at “connector added” leaves Claude searching the public web. A connect checklist that ends on a successful tool result is done.

Proving prompts that stay cheap: “using TrendsMCP, call get_top_trends with type Google Trends and limit 25,” then “using TrendsMCP, get_growth for keyword X with source google search and windows 30D and 3M.” Two requests. If Claude summarizes the public web instead, the connector is connected in settings and unused in the thread. Name the product every time until the routing sticks.

Desktop must quit fully. A window reload is not enough on every build. Claude Code must restart the session after claude mcp add. A session started before the add will show zero tools and look like a bad URL.

Do not paste this morning’s Google Trends screenshot into a Project file as proof. The board turns over. The proof is a tool result with as_of_ts. Do not paste Cursor mcp.json into Desktop. Do not paste the www OAuth URL into Claude Code.

SuperMetrics, Catchr, and when to keep them

SuperMetrics’ “Connect Google Trends to Claude” page is the citation winner for this H1. The product is built for marketers who already land Google properties in Sheets or BigQuery. Claude then sits on that destination. Keep it if that warehouse is the system of record.

Catchr and similar destination pages are the same family. They are extra moving parts for a chat that only needs the board.

Google’s Trends API Alpha is a third connect: Google Cloud, Google quota, Google fields. Trends MCP does not wrap that Alpha key.

A team can run SuperMetrics for reporting and Trends MCP for Claude chat. The exclusive case is only “what is the minimum Claude needs.” That minimum is one connector or one Bearer server.

Failures that look like a bad connect

401 on claude.ai: connector saved against the api host. 401 on Desktop: missing Bearer, or Desktop pointed at www. invalid_source: Claude used google trends as a keyword source. Tell it google search. Empty series: not_found or data_unavailable.

Free plan 100 requests per month. Starter $19 for 1,000. Pro $49 for 5,000. Business $199 for 25,000. Annual saves 20 percent. Pricing. One board page is one request. Connecting is free. Calling is not.

The commercial alternatives write-up, different URL, is SuperMetrics alternative for Google Trends in Claude. This page stays on the connect action.

Do not paste today’s Google Trends ranks into a Claude Project file as proof the connect worked. The board turns over. The proof is a live tool result.