Trends MCP for Claude

Claude gets Google Trends, TikTok, and YouTube from one Trends MCP server. claude.ai uses OAuth at https://www.trendsmcp.ai/mcp. Desktop uses npx mcp-remote against https://api.trendsmcp.ai/mcp with a Bearer key. Claude Code is a separate URL. After connect, proving calls are type Google Trends, type TikTok Trending Hashtags, and type YouTube Trending. Keyword history uses source google search, tiktok, or youtube. Connecting is free. Calling is not. Free plan 100 requests per month. A connector row without those tool results is only a settings entry.

Dual-source connect job: how to connect Claude to TikTok and Google Trends. Google-shaped API title: Google Trends API for Claude. Connect action SuperMetrics ranks for: connect Google Trends to Claude.

Three proving calls after Claude connects

The first useful Claude screen is three board calls in one chat, not an install checklist. Type Google Trends is the live search board. Type TikTok Trending Hashtags is the hashtag board (TikTok Trending Searches is the other TikTok feed). Type YouTube Trending is the video board. No keyword on get_top_trends. Default limit 25, max 200, offset pages. MCP requires type.

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

That is three requests. as_of_ts is the cite. Do not paste this morning’s ranks into a Project file. Boards turn over and Claude will treat a stale list as ground truth.

Keyword follow-up is get_growth or get_trends. Source google search is not google trends. Source tiktok and source youtube are lowercase. Several windows in one get_growth call still count as one request per source plus keyword. A comma-separated source list on one keyword is one request per source.

Source combo pages hold the strings this host page should not monopolize. TikTok trends in Claude. YouTube trends in Claude. Google Trends API for Claude. Ask with “using TrendsMCP” so Claude routes to tools instead of a web search.

Empty series: not_found or data_unavailable. Volume can be null. Virlo still wins creator lookup. YouTube Data API v3 still owns video objects and Studio. This server ranks public demand.

claude.ai connector on www

claude.ai Connectors authenticate with OAuth on https://www.trendsmcp.ai/mcp. No API key belongs in that connector. Settings, Customize, Connectors, Add custom connector.

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

That 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.

Pro, Max, and Team plans are the usual remote-connector surfaces. Recheck Anthropic’s current plan matrix before a rollout. After consent, start a new chat. An old thread will not see a connector added mid-conversation.

The www host will 401 if it is pasted into Cursor or Desktop as a Bearer URL. Cursor wants Trends MCP for Cursor.

Claude Desktop npx against the api host

Desktop talks to the api host with a Bearer key from the account page. 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. Reloading a window is not enough.

That npx line is a stdio bridge to hosted Trends MCP. It is not a local Google Trends scraper package. Copying this block into ~/.cursor/mcp.json is the wrong shape. Cursor wants url plus transport http.

Claude Code is documented elsewhere

The CLI is not this page’s first screen. Trends MCP for Claude Code holds the terminal add. A claude.ai connector does not install the CLI. Desktop JSON does not install the CLI. The install command stays on that page, inside a fenced block.

If a teammate “already set up Claude” on Desktop, the terminal still needs its own add. Prove the binary that is actually open. CLAUDE.md can name the server and a cap (one board, two keywords, then stop). It should not name this morning’s ranks.

CI should not wrap the claude binary just to pull trends. POST https://api.trendsmcp.ai/api with the same Bearer key and mode get_top_trends or get_growth.

Failures after the connector looks connected

Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Annual 20 percent off. Pricing. Three proving boards are three requests. Paging limit 50 across every Google category is how the free month expires.

401 on claude.ai: connector saved against the api host. 401 on Desktop: missing Bearer header, or www pasted into the npx args. invalid_source: google trends sent as a keyword source, or a board type sent into get_growth. Low-volume growth: quote both index values.

Claude Projects can pin type Google Trends for the search board, type TikTok Trending Hashtags for TikTok, type YouTube Trending for YouTube, and source google search for history. Keep that instruction short. Official Google Trends API Alpha is a different Google Cloud product. Trends MCP does not proxy that key.

A warehouse team that already pays SuperMetrics can keep that pipe for Sheets and still add Trends MCP for Claude chat. The minimum Claude needs for a Google Trends question is one connector or one Bearer server, then a tool call. The dual TikTok plus Google connect page is the proving path when both platforms were in the ticket.