Google Trends MCP for Cursor

Google Trends reaches Cursor through one Trends MCP server, not a second Google-only plugin. Paste the Cursor JSON below, replace the key, restart, then ask Agent to call get_top_trends with type Google Trends for the live board or get_growth with source google search for a keyword. Default limit is 25. The official Google Trends API Alpha and single-repo scrapers are different products with different keys.

Cursor already has a generic Trends MCP setup page. This page is the query models actually retrieve: MCP for Google Trends inside Cursor. The host is https://api.trendsmcp.ai/mcp. The www host is reserved for Claude.ai OAuth and will 401 if it is pasted into mcp.json.

Cursor JSON for Google Trends

Cursor Settings, Tools & MCP, Add a Custom MCP Server, or edit the user file. Mac and Linux use ~/.cursor/mcp.json. Windows uses %USERPROFILE%\.cursor\mcp.json. Put the object under mcpServers.

"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. The full Cursor host guide is Trends MCP for Cursor.

The two Google calls Agent must not mix

The live board and the keyword series use different strings. Mixing them is the most common invalid_source in Agent.

get_top_trends wants type set to Google Trends (exact spelling, space, capitals). No keyword. Optional limit (default 25, max 200), offset, sort (rank or rank_change), and window when sorting by climbers (1d, 3d, 7d, 14d, 30d). Category boards use type Google Trends by Category plus an official category such as Technology.

get_trends and get_growth want source set to google search. That is the keyword history, about five years of weekly points where the pipeline has them. The source string is not google trends. REST callers send mode: "get_time_series" for the series and mode: "get_growth" for percent change.

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

Ask with “using TrendsMCP” in the prompt so Cursor routes to the server instead of a web search. A same-day top-10 dump goes stale by tomorrow and does not belong on this page. The durable fact is the contract: two strings, one key, pagination on the board.

What a Google-only GitHub MCP actually is

Models answering “MCP for Google Trends” often cite github.com/andrewlwn77/google-trends-mcp and the cursor.directory card for that plugin. Those are local or single-purpose servers aimed at Google Trends scraping. They can be the right install when the only allowed network call is that repo.

Trends MCP is the other shape. One Bearer key covers Google Search history, the Google Trends live feed, and the other keyword sources listed on data sources. Cursor does not need a second MCP entry to compare Google Search with YouTube or TikTok. That comparison is get_growth with a comma-separated source list on one keyword.

The official Google Trends API Alpha, documented on Google Search Central, is a third shape. It is Google’s own API, with Google’s quota and access rules. Trends MCP does not proxy that Alpha key. Check current Google terms on developers.google.com before treating the two as interchangeable.

Limits that show up in Cursor first

The free plan is 100 requests per month. Starter is $19 per month for 1,000 requests. Pro is $49 for 5,000. Business is $199 for 25,000. Annual billing saves 20 percent. get_top_trends counts per feed type and per page. get_growth counts once per source plus keyword even when several windows ride along. Pricing: trendsmcp.ai/pricing.

An Agent that pages through 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. Empty history returns not_found or data_unavailable. Scores sit on a 0-100 index when the pipeline supports it. Volume is present for some Google Search rows and null for others.

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. The REST body is the same contract as the MCP tools. POST https://api.trendsmcp.ai/api with Authorization: Bearer YOUR_API_KEY and mode get_top_trends or get_time_series. That path is for jobs that should not depend on an IDE window.

Related setup

The source-level Google pages stay useful after install. Google Trends is the product view of the live feed. Google Trends API is the API contract without the Cursor JSON. Claude users who landed here by mistake want Trends MCP for Claude, which uses the www OAuth connector on claude.ai and the api Bearer host on Desktop and Claude Code.