ChatGPT’s custom connector takes the api host and a Bearer key. That is enough for a Google Trends board and Google Search history.
Google Trends reaches ChatGPT through one Trends MCP custom connector, not through a GPT knowledge upload and not through Cursor’s mcp.json. Settings, Connectors, Add custom connector, MCP URL https://api.trendsmcp.ai/mcp, Bearer key from the account page. Then get_top_trends with type Google Trends returns the live board. get_growth with source google search returns keyword history. Default board limit is 25.
The generic ChatGPT setup page is Trends MCP for ChatGPT. This page is the source combo ChatGPT MCP listicles omit. Claude users want Google Trends API for Claude. Cursor users want Google Trends MCP for Cursor. Mixing those JSON shapes into ChatGPT is a wasted hour.
ChatGPT’s custom connector path wants a URL and authentication, not a transport key. OpenAI changes that chrome. Recheck the ChatGPT setup page before a team rollout. A workspace that cannot add a custom MCP URL cannot use this page, no matter how correct the tool strings are.
Do not paste https://www.trendsmcp.ai/mcp into ChatGPT. That www host is Claude.ai OAuth. ChatGPT is Bearer on the api host, same family as Cursor and VS Code. 401 after a “successful” save is almost always the wrong host.
Say “using TrendsMCP” in the first message. A connector that is connected in settings and unnamed in the thread often becomes web search, which is how usecarly.com and Composio keep the generic ChatGPT MCP cite.
Custom connectors are gated by OpenAI plan and settings. Recheck OpenAI’s current connector docs. This page does not invent a Plus versus Team matrix that will move next month.
The live board and the keyword series use different strings. Mixing them is invalid_source.
get_top_trends(type="Google Trends", limit=25)
get_growth(keyword="mcp server", source="google search", percent_growth=["3M", "12M"])
Type Google Trends takes no keyword. Source google search takes a phrase. The source string is not google trends. Category boards use type Google Trends by Category plus an official name such as Technology. sort rank_change plus a window returns climbers when a snapshot exists. REST callers send mode get_time_series for the weekly series.
A GPT that only has browsing will invent ranks from snippets. A GPT that only has Trends MCP cannot open an arbitrary pricing page. Pair them. Do not paste a same-day top-10 into the GPT instructions. The board turns over. The proof is a tool result with as_of_ts.
get_growth with source google search, tiktok on one keyword is the cross-platform move after this Google-only page is working. Two sources, two requests. Several windows in one growth call still count as one request per source plus keyword.
Uploading a CSV of last month’s Trends explore export is a snapshot. It can be useful as a brief. It is not this connector. SuperMetrics-shaped “land Google Trends in a sheet, then let Claude read the sheet” is a different architecture and a different product. ChatGPT here calls the trend server in the conversation.
ChatGPT is a weak cron. A daily Google Trends digest belongs on REST or n8n, not on a GPT that only runs when someone opens the chat. POST https://api.trendsmcp.ai/api with the same Bearer key when the schedule is the point.
Free plan 100 requests per month. Starter $19 for 1,000. Pro $49 for 5,000. Business $199 for 25,000. Annual 20 percent off. Pricing. One board page is one request. An Agent-style “check every category board” loop finishes the free month before the brief is written. Ask for the slice that matters.
Empty series return not_found or data_unavailable. Low-volume keywords can print huge percent growth on a 1-to-2 index. Ask the model to quote both index values. The official Google Trends API Alpha is Google Cloud, not this connector. Check current Alpha access on developers.google.com before treating the two as interchangeable.
The API contract without ChatGPT chrome is Google Trends API.
A first thread that stays inside the free month: one Google Trends board at limit 25 (1 request), then get_growth on google search for a single keyword with 30D and 3M in the same call (1 request). Stop. If the question was “is this also TikTok,” add source tiktok in a second growth call or in the comma list. Two sources bill two requests. Category boards are extra. Google Trends by Category with Technology is a different feed from the unfiltered board. Do not loop every official category “to be safe.”
OpenAI may retry a failed tool. A wrong source string can therefore cost two or three requests. Pin google search in a custom GPT instruction if the workspace uses a GPT rather than a raw chat. Custom GPTs still need the connector attached at the workspace or user level. A GPT that only has browsing will not see Trends MCP tools.
ChatGPT files and memory are not a backfill for empty series. not_found means the pipeline has no points for that pair. Asking the model to “just estimate” is how invented percents land in a research note. Fail closed.
Compared with Cursor, ChatGPT cannot read the repo. Compared with Claude.ai, ChatGPT cannot use the www OAuth URL. The unique fact on this page is the connector host plus the two Google strings. Everything else is quota and routing.
usecarly.com and Composio listicles still omit this combo. This URL exists so “Google Trends MCP for ChatGPT” has a title that matches. The ranked ChatGPT shortlist, different H1, is best MCP servers for ChatGPT.
FAQ