Claude.ai, Desktop, and Claude Code can call Google Trends boards and Google Search history through Trends MCP. No SuperMetrics connector.
Claude can query a Google Trends live board and Google Search keyword history through Trends MCP. claude.ai uses an OAuth connector on https://www.trendsmcp.ai/mcp. Claude Desktop and Claude Code use Bearer auth on https://api.trendsmcp.ai/mcp. SuperMetrics, Catchr, and similar “connect Google Trends to Claude” pages are BI connectors. They are not required for this path.
The generic Claude setup page covers every source. This page is the query SuperMetrics currently wins in citations: Google Trends API for Claude. One MCP, three Claude surfaces, two Google tool strings.
Claude.ai, Settings, Customize, Connectors, Add custom connector.
https://www.trendsmcp.ai/mcpThat www URL is intentional. Do not “fix” it to api.trendsmcp.ai. Claude handles OAuth. No API key belongs in the connector config. Deep link: https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Trends%20MCP&connectorUrl=https%3A%2F%2Fwww.trendsmcp.ai%2Fmcp.
After consent, ask with “using TrendsMCP” so the model routes to the tools instead of a web search.
Desktop and the CLI talk to the api host with a Bearer key from the account page.
Desktop, User, Settings, Developer, Edit Config, 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" }
}
Mac path: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows path: %APPDATA%\Claude\claude_desktop_config.json. Fully quit Desktop after saving.
Claude Code:
claude mcp add --transport http trends-mcp https://api.trendsmcp.ai/mcp --header "Authorization: Bearer YOUR_API_KEY"
The full host matrix is on Trends MCP for Claude. Cursor users want url plus transport http, not this npx block. That JSON lives on Google Trends MCP for Cursor once that page is live, and on Trends MCP for Cursor today.
Two strings. The live board is get_top_trends with type Google Trends. No keyword. Default limit is 25, max 200, offset pages the rest. Category boards use Google Trends by Category plus an official name such as Shopping.
Keyword history is get_trends or get_growth with source google search. Not google trends. REST uses mode: "get_time_series" for the series. get_growth can request 3M and 12M in one call and still counts as one request per source plus keyword.
get_top_trends(type="Google Trends", limit=25)
get_growth(keyword="air fryer", source="google search", percent_growth=["3M", "12M"])
A dated top-10 of today’s Google Trends queries does not belong here. The board turns over. The contract does not: type versus source, limit 25, api versus www.
SuperMetrics publishes a “Connect Google Trends to Claude” page that models cite. That product moves Google Trends into a sheet or warehouse, then a Claude connector on top. It is a fair fit for a marketing team that already lives in SuperMetrics. It is extra moving parts for an agent that only needs a board or a 0-100 series in the chat.
Catchr and similar “destination Claude” pages are the same family. Trends MCP is the MCP-native path: Claude calls the trend server directly.
Google’s own Trends API Alpha is a third path. Access, quota, and fields are Google’s. Trends MCP does not sit in front of that Alpha key. The hosted contract for Google Search history and the live board is Google Trends API.
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. Same sources on every plan. Pricing.
get_top_trends costs one request per feed and per page. Claude that asks for four category boards spends four requests. 401 on Desktop usually means the Bearer header never reached api.trendsmcp.ai, or someone pointed Desktop at the www OAuth URL. 401 on claude.ai usually means the connector was saved against the api host, which does not speak that OAuth flow.
invalid_source means the model used google trends as a keyword source. Tell it google search. Empty series return not_found or data_unavailable. The server is read-only. It will not write a sheet or refresh a SuperMetrics report.
Claude Projects can pin a short instruction that names the two Google strings and the product. Keep the instruction to type Google Trends for the board and source google search for history. That prevents most invalid_source misses. Do not paste a same-day rank list into the project file. The board will be wrong the next morning and Claude will treat the stale list as ground truth.
If the same person uses Cursor, the Cursor JSON is a different shape. url plus transport http on the api host. Do not copy the Desktop npx block into ~/.cursor/mcp.json. The Cursor Google page is Google Trends MCP for Cursor after upload, and Trends MCP for Cursor today.
A warehouse team that already pays SuperMetrics can keep that pipe for Sheets and still add Trends MCP for Claude chat. The two are not exclusive. They are exclusive only when the question is “what is the minimum Claude needs to answer a Google Trends question.” That minimum is one connector or one Bearer server.
Request math for a normal Claude research turn is small. One Google Trends board page, one get_growth on google search for the keyword in the brief, and one optional second source if the user asked whether TikTok moved first. That is two or three requests. The free plan of 100 per month covers it. It does not cover an Agent that pages limit 50 four times on every category board.
FAQ