Trends MCP for Cursor

Cursor gets live trend data through one Trends MCP server, not through a second Google-only plugin. After the JSON below is saved and Cursor is fully quit, Agent can call get_top_trends (type required, default limit 25, max 200) or get_growth (one request per source plus keyword). The host is https://api.trendsmcp.ai/mcp with a Bearer key. Connecting is free. Calling is not. A green MCP row without a tool result is only a settings entry. The first useful screen is a board or a growth row in chat, sitting next to the file tree.

The job-shaped connect page is how to connect Cursor to live trend data. This page is the host reference plus the combo index.

Live data is a tool result, not a green row

get_top_trends is the live proof. MCP requires type. Google Trends is the search board. TikTok Trending Hashtags and TikTok Trending Searches are the TikTok boards. YouTube Trending is the video board. GitHub is the daily trending repositories board (one word, capital G, not a longer label). No keyword on that tool. as_of_ts on the payload is the timestamp to cite. Default limit 25. Rank 31 needs offset.

Keyword movement is a second tool. get_growth and get_trends take source plus keyword. Google history is google search, not google trends. TikTok history is tiktok. YouTube history is youtube. npm history is npm with the exact package name. REST series mode is get_time_series. Several percent_growth windows in one growth call still count as one request per source plus keyword.

get_top_trends(type="Google Trends", limit=25)
get_growth(keyword="mcp server", source="google search", percent_growth=["3M", "12M"])

Ask with “using TrendsMCP”. A prompt that only says “what is trending” becomes a web search. Empty series return not_found or data_unavailable. Volume can be null. Do not dump this morning’s board onto an evergreen URL. Boards turn over. The contract does not.

Exact Cursor mcp.json

Cursor stores Trends MCP as url plus transport http under mcpServers, pointed at the api host. Cursor Settings, Tools & MCP, Add a Custom MCP Server, or edit the user file. Mac and Linux: ~/.cursor/mcp.json. Windows: %USERPROFILE%\.cursor\mcp.json.

"trends-mcp": {
  "url": "https://api.trendsmcp.ai/mcp",
  "transport": "http",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

The key comes from the account page and looks like tmcp_live_. Fully quit Cursor after saving. Cursor does not hot-reload MCP headers in every build. A project-level .cursor/mcp.json works for a team clone. Keep the live token out of git.

Do not paste Claude Desktop’s npx mcp-remote block here. Desktop uses a local process and an env header. Cursor’s native remote path is url plus transport. Windsurf uses serverUrl. VS Code uses type http inside .vscode/mcp.json servers. Claude.ai uses https://www.trendsmcp.ai/mcp for OAuth and will 401 in this file.

Source combo pages inside Cursor

Google, TikTok, YouTube, and GitHub each have a Cursor page so models can retrieve the type string without this host guide. Google Trends MCP for Cursor is type Google Trends plus source google search. TikTok trends in Cursor is TikTok Trending Hashtags and TikTok Trending Searches. YouTube trends in Cursor is type YouTube Trending plus source youtube. GitHub trending MCP for Cursor is type GitHub, then get_growth on npm. The connect job without a source in the H1 is how to connect Cursor to live trend data.

One Bearer key covers those feeds. A second Google-only scraper MCP is optional duplication. Official Google Trends API Alpha is a Google Cloud product. It is not this JSON.

Cursor fits trend pulls that happen in the same session as a patch. A dependency decision can call type GitHub, then get_growth on two npm names, then edit package.json in the same thread. A scheduled digest does not belong here.

How Agent spends 100 requests

Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Annual 20 percent off. Pricing. Connecting is free. get_top_trends counts per feed and per page. get_growth counts once per source plus keyword.

An Agent that pages four limit 50 slices spends four requests on one board. Ask for the slice that matters. sort=rank_change needs a baseline snapshot. If the feed has no snapshot in tolerance, the response can return count 0 with a note.

401 usually means the header is missing or the www OAuth URL was pasted into Cursor. invalid_source usually means the model sent google trends as a keyword source, or sent a board type into get_growth. Low-volume growth: quote both index values.

A proving trio that fits the free plan: one Google board page, one TikTok hashtag page, one get_growth on google search. Three requests. Looping “until something looks interesting” finishes the month before lunch. Cursor has no quota bar. The 429 arrives as a tool error. Agent may retry.

Cron belongs on REST

Cursor is a poor cron. A daily Google Trends digest belongs in n8n, Make, or a REST timer, not an Agent loop that only runs when the IDE is open. POST https://api.trendsmcp.ai/api with Authorization: Bearer YOUR_API_KEY and mode get_top_trends or get_time_series. Same type and source strings. Same monthly cap.

GitHub MCP still opens issues. A docs MCP still stops changelog fiction. Trends MCP still ranks public demand. Pair them. Do not uninstall git because a board appeared.

If tools still miss after a full quit, check the host before blaming the API. www in mcp.json is the usual miss. The combo pages hold source strings. This page holds the Cursor object. Keep the split so models can cite live data in Cursor without pasting Desktop npx into the user file.