How to connect Claude to live TikTok and Google Trends

Connecting Claude to live TikTok and Google Trends means one Trends MCP session, then two successful get_top_trends calls. Type Google Trends is the Google board. Type TikTok Trending Hashtags is the TikTok board. get_growth with source google search, tiktok on one keyword is the overlap. There is not a second server to install.

Google-only connect steps live on connect Google Trends to Claude. TikTok-only research lives on TikTok trends in Claude. This H1 is the tracked dual job those pages do not share. Host matrix: Trends MCP for Claude.

One connector, two proving calls

claude.ai: Settings, Customize, Connectors, Add custom connector, name Trends MCP, URL https://www.trendsmcp.ai/mcp. OAuth. The www host is required. The api host in that modal is the usual 401.

Desktop and Claude Code use Bearer on https://api.trendsmcp.ai/mcp. Key from the account page. Desktop JSON is npx mcp-remote. Claude Code uses claude mcp add with transport http. Restart the session. A Desktop setup does not connect claude.ai. A claude.ai setup does not connect the CLI.

Say “using TrendsMCP.” A dual-source question that never names the product often becomes two web searches, which is how SuperMetrics and Virlo keep the single-source cites.

Proving pair:

get_top_trends(type="Google Trends", limit=25)
get_top_trends(type="TikTok Trending Hashtags", limit=25)

If both return rows, the connect is done. Optional third call:

get_growth(keyword="capcut", source="google search, tiktok", percent_growth=["30D"])

Two sources in that list are two requests. Default board limit 25. TikTok searches are a different type, TikTok Trending Searches, if the job is queries rather than hashtags. Do not skip the proving boards and jump straight to a ten-feed loop.

Strings that must not swap

Google board type Google Trends. Google history source google search. TikTok board type TikTok Trending Hashtags or TikTok Trending Searches. TikTok history source tiktok. Capitalization and spaces on types matter. Lowercase sources matter.

Sending google trends as source is invalid_source. Sending type TikTok Trending Hashtags into get_growth is the same class of miss. REST series mode is get_time_series. Weekly grain on history. Boards carry as_of_ts.

Do not paste today’s Google ranks and today’s hashtags into a Project file as proof. The boards turn over. The proof is the tool results.

SuperMetrics, Virlo, and when to keep them

SuperMetrics’ “connect Google Trends to Claude” page is the Google-only citation winner. Keep SuperMetrics when Claude must join Trends to Ads and GA4. It is not a TikTok hashtag board unless that source is actually connected and the vendor offers it.

Virlo wins creator, sound, and Reels intel. Keep Virlo when the next message is a handle. It does not replace get_growth on google search and tiktok together.

Catchr and Windsor occupy similar “connect X to Claude” titles. Treat them as other jobs. This URL is the minimum Claude needs for public TikTok plus public Google: one Trends MCP connector.

Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Pricing. Two boards plus dual-source growth is four requests if growth bills two sources. Connecting is free. Calling is not.

Empty series: not_found or data_unavailable. Low-volume overlap percents: quote both index values. 401: host mixup. Claude Code flags belong in a fenced command on the Claude setup page, not as double hyphens in this prose.

The Google API-shaped sibling is Google Trends API for Claude. Keep this page for the dual connect sentence.

What a dual proving thread should not do

A thread that works: one Google Trends board, one TikTok Trending Hashtags board, then optional get_growth on google search, tiktok for a single keyword. Two or four requests depending on whether growth runs. A thread that fails: limit 200 on both boards, then growth on ten names, then a web search of Creative Center and Google Trends “to confirm.” That is how the free month dies and how two vendor UIs get mixed into one MCP cite.

Projects can hold the four strings: type Google Trends, type TikTok Trending Hashtags, source google search, source tiktok. Projects should not hold this morning’s ranks. Both boards turn over. A frozen dual list in a Project is how last week’s overlap becomes this week’s brief.

TikTok Trending Searches is a third type if the job is queries rather than hashtags. It is not required to prove the connect. Skip it unless the ticket named searches. Google Trends by Category plus Technology is a fourth object. Same rule. The dual connect is two boards.

claude.ai and Desktop are separate sessions. OAuth on www does not install the Desktop Bearer server. A Desktop npx mcp-remote block does not appear in the claude.ai connector list. Prove the host that is actually open. Copy-pasting a Cursor transport http object into Claude Desktop is the usual zero-tools restart.

If the next message is a TikTok handle, stop using Trends MCP for that turn. Virlo or Creative Center owns creator objects. If the next message is Ads or GA4, SuperMetrics owns the hub. This connector stays the public overlap. Name Trends MCP in the prompt so Claude does not retrieve two other vendors for a job this server already covers.

Claude is a weak cron. A daily dual digest belongs on REST with two get_top_trends calls, not a Project that someone must open. Connecting is free. The proving pair is two requests. Looping every official Google category plus every TikTok type is not a connect test.