Integrations

get_growth in Cursor

Cursor Agent calls get_growth after Trends MCP is saved with url and a Bearer key. The proving call is a keyword percent window, not a trending board.

Live data as of 2026-11-17

Cursor Agent pulls keyword percent change through Trends MCP get_growth after the Cursor object is saved at https://api.trendsmcp.ai/mcp with a Bearer key. Cursor Settings, Tools & MCP, Add a Custom MCP Server, or edit ~/.cursor/mcp.json. Cursor docs fetched 2026-11-17 show a remote server as url plus headers. Homepage copy-config from the same morning matches that shape. Dedicated Trends MCP for Cursor still adds transport http. Ask, using TrendsMCP, for a keyword source such as Google Search plus a phrase. Omit percent_growth and the window is still 12M. A 2026-11-17 nike Google Search call printed index 58.0 on 2026-11-14 versus 65.0 on 2025-11-15, growth -10.77 percent, across 261 weekly points.

Cursor JSON on the api host, then name get_growth

Host setup lives on Trends MCP for Cursor. The connect job lives on how to connect Cursor to live trend data. Those pages prove the connect with get_top_trends. This page is the growth-shaped call those guides never name.

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. Under mcpServers, Cursor docs fetched 2026-11-17 from https://cursor.com/docs/mcp print this remote shape:

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

Homepage copy-config fetched 2026-11-17 wraps the same object:

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

llms-full.txt from the same morning inlines that Cursor block without transport. Dedicated Trends MCP for Cursor still publishes transport http next to url. How to connect Cursor to live trend data does the same. This run did not click Add a Custom MCP Server and did not fully quit a Cursor desktop. It recorded both published objects. Both hit the api host with a Bearer key. Do not paste https://www.trendsmcp.ai/mcp into this file. That www host is OAuth for Claude and ChatGPT. A Bearer header against www 401s.

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 green MCP row without a tool result is only a settings entry.

Ask with "using TrendsMCP" so Agent routes to the server instead of a web search. The proving prompt is a growth call, not a board call.

get_growth(keyword="nike", source="google search")
get_growth(keyword="nike", source="google search, youtube", percent_growth=["3M", "12M"])

get_top_trends with type Google Trends still ranks a live board. That is a different tool. Do not send a board type string into get_growth. The dedicated Cursor page still tells the model to call get_trends for keyword history. The live MCP list in this session advertised get_time_series, get_growth, get_top_trends, get_context, get_reviews, and get_usage. Six tools. Five of them bill. get_usage is free. get_top_posts is absent. get_ranked_trends is absent.

Nightly growth tracking belongs on REST, not an Agent loop that only runs when the IDE is open. POST https://api.trendsmcp.ai/api with a Bearer key and mode get_growth. Wrapping Cursor Agent in a scheduled task just to pull windows is a roundabout way to hit that URL.

Project mcp.json can hold the server without the live token

Cursor docs fetched 2026-11-17 document two files. Global: ~/.cursor/mcp.json. Project: .cursor/mcp.json in the repo. Cursor help at https://cursor.com/help/customization/mcp says both files are merged, and the project-level config takes priority when the same server name appears in both.

Remote headers accept config interpolation. Cursor resolves ${env:NAME} inside url and headers. A committed project file can look like this:

"trends-mcp": {
  "url": "https://api.trendsmcp.ai/mcp",
  "headers": {
    "Authorization": "Bearer ${env:TMCP_API_KEY}"
  }
}

Keep the live token out of git. Each developer sets the variable in a shell profile. Cursor docs also list ${userHome} and ${workspaceFolder}. envFile is STDIO-only. Remote HTTP entries do not load a .env file that way.

STDIO servers in those same docs require type stdio plus command. Remote HTTP entries in the official remote example do not carry a transport field. That is why homepage copy-config can look pasted-complete without transport, while older Cursor product pages still include it.

Do not paste Claude Desktop's npx mcp-remote block. Do not paste ChatGPT's www OAuth URL. Windsurf wants serverUrl. VS Code wants type http under servers.

A .cursorrules or AGENTS.md file can name get_growth, keyword sources such as Google Search, YouTube, and Amazon, and a cap of one source then stop. It should not freeze this morning's nike indexes. Those points move. A frozen percent in the repo becomes a stale architecture note.

Omit percent_growth and the window is still 12M

A 2026-11-17 MCP get_growth call that sent source Google Search and keyword nike with no percent_growth field printed one 12M row and metadata.calculations_completed 1. Recent index 58.0 on 2026-11-14 00:00:00+00:00. Baseline 65.0 on 2025-11-15 00:00:00+00:00. Growth -10.77 percent, direction decrease, 261 weekly points. volume_available true, volume_estimated true, recent_volume 26,500,000, baseline_volume 29,600,000. volume_growth was null, with volume_growth_omitted_reason set to "volume is derived from the trend value for this source, not an independent measurement". Quote the 0-100 value. Treat that volume label as derived.

A second call that sent six presets completed 6 calculations on the same 261 points. Alias pairs that shared dates and growth on that nike series:

LabelsBaseline dateBaseline indexGrowth
7D and 1W2026-11-0753.0+9.43%
12M and 1Y2025-11-1565.0-10.77%

Recent index was 58.0 on 2026-11-14 for every row. Windows that did not collapse into those aliases still shared that recent point. YTD was 0.0 percent from 58.0 on 2026-01-03, direction flat. 3M was -13.43 percent from 67.0 on 2026-08-15. Same 58.0, four different baselines. For comma-separated sources in one get_growth body, see the multi-source growth API. The shared window table lives on get_growth.

Preset strings on MCP are 7D, 1W, 14D, 2W, 30D, 1M, 2M, 3M, 6M, 9M, 12M, 1Y, 18M, 24M, 2Y, 36M, 3Y, 48M, 4Y, 60M, 5Y, MTD, QTD, and YTD. Named {name, recent, baseline} objects are REST-only. REST mode growth with source Google Search, keyword nike, and percent_growth ["12M"] printed the same 58.0 versus 65.0 row. A REST body that sent {"name": "yoy", "recent": "2026-10-31", "baseline": "2025-11-01"} printed 52.0 versus 53.0, growth -1.89 percent, plus recent_requested and baseline_requested. Those snap fields are the REST custom-date contract. Do not send a date object to MCP and expect them.

MCP source Google Trends on keyword nike returned 400 invalid_source, message 'google trends' is not a valid source. The valid_sources array named google search, google images, google news, google shopping, youtube, wikipedia, tiktok, amazon, app downloads, app rankings, steam, npm, python, pinterest, and all. That list is the keyword-history contract. Type Google Trends belongs on get_top_trends. Keep the board call on that type string.

A 2026-11-17 get_growth call that sent source Reddit and keyword nike returned 400 source_disabled, message 'reddit' is temporarily disabled for get_growth. Try another source. The same valid_sources list followed. news sentiment used the same source_disabled code. OpenAPI's Error.error enum, fetched the same morning, still lists invalid_source and growth_calculation_failed. It does not list source_disabled. A generated client that only maps that enum will not name the failure Agent just hit.

Amazon is still a growth source. Keyword air fryer on source Amazon with windows 7D, 1M, and 12M printed 52 monthly points and metadata.all_successful false. 7D returned error collapsed_range with message "Recent and baseline resolved to the same data point; not enough history for this preset". 1M succeeded on 2026-10-31 versus 2026-09-30: index 67.9 versus 59.7, +13.74 percent, volumes 7,350,631 versus 6,465,752, volume growth +13.69 percent. 12M was -5.83 percent from 72.1 / 7,802,064 on 2025-10-31. A Cursor prompt that mixes Amazon 7D with Google Search 7D will look broken on Amazon and fine on Search. Read status per row.

The live google-search-vs-reddit page still documents source reddit on get_growth as a working daily community series. That 400 is the current contract. Do not send Agent a .cursorrules line that names reddit as a keyword source until the disable lifts.

Extra windows ride on one source. A comma list does not.

Docs price get_growth per source in the call, every window included. The six-window nike Google Search call and the default 12M call are both one unit. Extra percent_growth strings do not add units. source all is the expensive exception: the MCP schema says that alias expands to 9 keyword sources and costs 9. Do not ask Agent to "compare every platform" in one sitting.

A comma list is the other meter. source Google Search, YouTube with windows 12M and 3M printed requests_charged 2, sources_successful 2, and growth_specs_count 2. Google Search matched the 12M -10.77 percent and 3M -13.43 percent rows above. YouTube printed 261 points, 12M 42.0 versus 44.0 on 2025-11-15 (-4.55 percent), and 3M 42.0 versus 43.0 on 2026-08-15 (-2.33 percent). YouTube rows in this pull omitted volume fields. volume_weighted_growth used Google Search alone: -10.77, sources_with_volume 1, weight_coverage 1/2 sources. Read source_results before treating that mixer as a two-platform number.

Connecting is free. Calling is not. get_usage during this run printed Business 8,320 of 25,000 used at the start, then 8,329, reset 2026-12-01. cost_rule: 1 request per data type in a call; get_top_trends: 1 request per 10 rows per board (limit defaults to 100). Only data types that answer are charged. buy_credits_url on that payload still uses the apex account billing tab:

https://trendsmcp.ai/account?tab=billing

Site links on this page stay on www. pricing.md fetched 2026-11-17 already publishes the www billing tab.

A garbage REST mode getgrowth returned envelope statusCode 400, error invalid_mode, and valid_modes get_context, get_growth, get_reviews, get_time_series, get_top_trends. The aliases object named growth for get_growth and reviews for get_reviews. It omitted get_context. REST still serves the dropped posts mode. POST https://api.trendsmcp.ai/api with mode get_top_posts, source tiktok, keyword fitness, and limit 1 returned HTTP 200, count 1, and https://www.tiktok.com/@treandsara/video/7705638158607682829, posted 2026-11-08, 2,400,000 plays, 137,700 likes. Cursor Agent that reads the live MCP list will not offer that call. The existing get-top-posts-in-cursor page still tells Agent to call it.

OpenAPI 3.1 at https://www.trendsmcp.ai/openapi.json, fetched 2026-11-17, describes GetGrowthRequest with alias growth and REST-only custom date objects. GetContextRequest has hashtag and omits comments. components.schemas still has no GetReviewsRequest. The mode discriminator mapping lists get_context, get_growth, get_time_series, and get_top_trends only. GetTopTrendsRequest still defaults limit to 25. MCP and get_usage cost_rule default the board to 100. HTML /docs grepped 1 leftover get_top_posts comment and 0 for GetReviewsRequest.

Free plan 100 requests a month. Starter $19 for 1,000. Pro $49 for 5,000. Business $199 for 25,000. One Google Search call plus one YouTube call is two requests. Looping source all finishes the free plan before the .cursorrules file is written. Check current pricing before locking a budget.

Common questions

Paste Trends MCP under mcpServers with url https://api.trendsmcp.ai/mcp and a Bearer key. Mac and Linux use ~/.cursor/mcp.json. Windows uses %USERPROFILE%\.cursor\mcp.json. Fully quit Cursor. Ask Agent, using TrendsMCP, for get_growth with a keyword source such as Google Search and a phrase. Omit percent_growth and a 2026-11-17 nike Google Search call still printed one 12M row: index 58.0 on 2026-11-14 versus 65.0 on 2025-11-15, growth -10.77 percent, across 261 weekly points.
Cursor docs fetched 2026-11-17 from https://cursor.com/docs/mcp print a remote server as url plus headers, with no transport field. Homepage copy-config and llms-full.txt from the same morning match that shape. Dedicated Trends MCP for Cursor and how to connect Cursor to live trend data still add transport http. This run recorded both published objects and did not click Add a Custom MCP Server. Both hit the api host. Do not paste the www OAuth URL into this file.
The default is 12M. On 2026-11-17, nike on Google Search with no percent_growth field returned a single 12M row, the same -10.77 percent print as the 12M row inside a six-window call. 7D matched 1W at +9.43 percent from 53.0 on 2026-11-07. 1Y matched 12M. YTD used 2026-01-03 and printed 0.0 percent, direction flat. Extra presets in one body still count as one source-keyword request.
Google Trends is a get_top_trends feed type, not a get_growth source. MCP source Google Trends on keyword nike returned 400 invalid_source, message 'google trends' is not a valid source, plus the keyword list: google search, google images, google news, google shopping, youtube, wikipedia, tiktok, amazon, app downloads, app rankings, steam, npm, python, pinterest, all. Ask Agent for source google search on get_growth, and type Google Trends on get_top_trends.
Yes. POST https://api.trendsmcp.ai/api with mode get_growth, or the alias growth. A 2026-11-17 REST body with mode growth, source Google Search, keyword nike, and percent_growth 12M printed the same 58.0 versus 65.0 row as MCP. Custom {name, recent, baseline} objects are REST-only; MCP takes the string windows. Nightly growth pulls belong on REST, not an Agent loop that only runs when the IDE is open.