MCP & API Reference
Query behavioral trend data across search, social, and commerce platforms. Use MCP to query via an AI assistant like Claude or ChatGPT, or the REST API to integrate directly into your code.
Get your free API key
By continuing you agree to our Terms & Privacy Policy.
Nothing there? Check spam or .
What are you working on?
How will you connect?
Sign in to your account
API key sent to your inbox. Sign in to access your dashboard.
Connect
Add to your AI in 30 seconds
How will you connect to TrendsMCP?
Which client are you using?
Or configure manually
Cursor Settings → Tools & MCP → Add a Custom MCP Server
"trends-mcp": { "url": "https://api.trendsmcp.ai/mcp", "transport": "http", "headers": { "Authorization": "Bearer YOUR_API_KEY" } }
Mac / Linux — ~/.cursor/mcp.json
Windows — %USERPROFILE%\.cursor\mcp.json
↑ Sign up above first to get your API key — the config won't work without it.
Three steps: open Claude, review the pre-filled form, click Add.
In Claude: Settings → Customize → Connectors → Add custom connector. The link above does this for you. Use https://www.trendsmcp.ai/mcp for Claude Connectors (OAuth) or https://api.trendsmcp.ai/mcp for direct MCP config; both reach the same service.
Or configure manually
User → Settings → Developer → Edit Config — add 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 — ~/Library/Application Support/Claude/claude_desktop_config.json
Windows — %APPDATA%\Claude\claude_desktop_config.json
Fully quit and restart Claude Desktop after saving.
Claude Code (CLI)
claude mcp add --transport http trends-mcp https://api.trendsmcp.ai/mcp \ --header "Authorization: Bearer YOUR_API_KEY"
Windsurf
Settings → Advanced Settings → Cascade → Add custom server +
"trends-mcp": { "url": "https://api.trendsmcp.ai/mcp", "transport": "http", "headers": { "Authorization": "Bearer YOUR_API_KEY" } }
Mac / Linux — ~/.codeium/windsurf/mcp_config.json
Windows — %USERPROFILE%\.codeium\windsurf\mcp_config.json
Or: Command Palette → Windsurf: Configure MCP Servers
VS Code
Extensions sidebar → search @mcp trends-mcp → Install — or paste manually into .vscode/mcp.json inside servers
"trends-mcp": { "type": "http", "url": "https://api.trendsmcp.ai/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } }
Paste into .vscode/mcp.json, or:
Command Palette (⇧⌘P / Ctrl+Shift+P) → MCP: Add Server
Authentication
An account is required to connect — both for MCP and the REST API. Sign up for free with your email and we'll send your API key instantly (100 requests/month, no credit card). Every request must then include that API key as a Bearer token in the Authorization header. How calls are counted is defined below (same rules for REST and MCP).
curl -X POST https://api.trendsmcp.ai/api \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"source":"google search","keyword":"bitcoin"}'import requests
res = requests.post(
"https://api.trendsmcp.ai/api",
headers={"Authorization": "Bearer YOUR_API_KEY"},
json={"source": "google search", "keyword": "bitcoin"}
)
res.raise_for_status()
data = res.json()const res = await fetch("https://api.trendsmcp.ai/api", {
method: "POST",
headers: {
"Authorization": "Bearer YOUR_API_KEY",
"Content-Type": "application/json"
},
body: JSON.stringify({ source: "google search", keyword: "bitcoin" })
});
const data = await res.json();What counts as a request
Each successful hit against the data API uses one unit of your monthly quota.
One source + keyword per HTTP request or MCP tool call counts as one request.
One source + keyword per call counts as one request, including every entry in percent_growth in that same call.
Counted per feed (type) and per page. Example with limit 25: offset 0 is one request, offset 25 is another for the same type. Different feeds are separate. If one response includes several feeds, each feed is counted per page on its own.
Data Sources
Two types of sources are available, accessed via different operations. Keyword sources return a historical time series or growth metric for a specific keyword. Live feeds return the top-ranked items on a platform right now. No keyword needed.
Keyword sources (Get Trends & Get Growth)
Pass the source value below in your request body alongside keyword. For Get Growth, pass one source or a comma-separated list (e.g. amazon, tiktok, youtube). For Get Trends, pass one source per request. Scores are normalized to a 0–100 scale where the pipeline supports it.
| source | Description | Keyword format |
|---|---|---|
google search | Google search volume | Any keyword or phrase |
google images | Google image search volume | Any keyword or phrase |
google news | Google News search volume | Any keyword or phrase |
google shopping | Google Shopping search volume | Any keyword or phrase |
youtube | YouTube search volume | Any keyword or phrase |
tiktok | TikTok hashtag volume | Hashtag or topic |
reddit | Subreddit subscribers | Subreddit name only, no r/ prefix |
amazon | Amazon product search volume | Product name or category |
wikipedia | Wikipedia page views | Article title or topic |
news volume | News article mention volume | Any keyword or phrase |
news sentiment | News sentiment score (positive / negative) | Any keyword or phrase |
app downloads | Android app download estimates (AppBrain) | Android bundle ID e.g. com.openai.chatgpt |
app rankings | Android app store ranking charts (AppBrain) | Android bundle ID e.g. com.himshers.hims |
npm | npm package weekly downloads | Exact package name, case-sensitive e.g. react, @babel/core |
steam | Steam concurrent players (monthly) | Game display name e.g. Elden Ring (first Steam search result) |
Live feeds (Get Top Trends)
Pass the type value below with mode: "top_trends". No keyword needed. Optional category filter for Amazon Best Sellers by Category and Top Websites. Returns the current ranked leaders on that platform (e.g. the top 25 trending hashtags on TikTok right now).
| type | Platform / feed |
|---|---|
Google Trends | Top trending search terms on Google right now |
Google News Top News | Top news stories from Google News |
TikTok Trending Hashtags | Top trending hashtags on TikTok |
YouTube Trending | Top trending videos on YouTube |
X (Twitter) Trending | Top trending topics on X |
Reddit Hot Posts | Hottest posts on Reddit's front page |
Reddit World News | Top posts in r/worldnews |
Wikipedia Trending | Most-viewed Wikipedia articles today |
Amazon Best Sellers Top Rated | Amazon top-rated best sellers across all categories |
Amazon Best Sellers by Category | Amazon best sellers filtered by product category |
App Store Top Free | Top free apps on the iOS App Store |
App Store Top Paid | Top paid apps on the iOS App Store |
Google Play | Top apps on Google Play |
Top Websites | Most-visited websites globally by traffic rank |
Spotify Top Podcasts | Top podcasts on Spotify |
Steam Most Played | Top games by concurrent live players |
GitHub Trending Repos | Daily trending repositories across all languages |
IMDb MOVIEmeter | Top 100 most-popular movies by user activity |
Open Library Trending Books | Daily trending books from Open Library |
About this data
Trends MCP is an independent analytics service. Output consists of proprietary estimates produced through aggregation, normalization, and modeling of publicly observable signals. Index scores and volume-like figures are not official metrics from any third-party platform. See our Terms of Service for details.
Routing
All requests go to a single POST / endpoint. The operation is selected by the fields you include in the request body.
| Operation | Required fields |
|---|---|
| Get Trends | source + keyword (no percent_growth) |
| Get Growth | source + keyword (percent_growth optional, defaults to ["12M"]) |
| Get Top Trends | mode: "top_trends" |
/Get Trends
Returns a full historical time series for a keyword from a single source. Approximately 5 years of weekly data. Values normalized to 0–100 where the pipeline supports it. Specify one source per request.
Quota: 1 request per source + keyword. Full rules
Request body
| Field | Type | Required | Description |
|---|---|---|---|
source | string | Required | One source per request. See Data Sources. |
keyword | string | Required | Keyword, brand, product, or topic. |
data_mode | string | Optional | Weekly only — approximately 5 years of historical trends. Omit when using MCP. |
Response fields
| Field | Type | Description |
|---|---|---|
date | string | ISO 8601 date e.g. "2026-03-21" |
value | number | Normalized trend score, 0–100. |
volume | number | null | Absolute volume where available. null otherwise. |
keyword | string | The keyword queried. |
source | string | The data source used. |
{
"source": "google search",
"keyword": "bitcoin",
"data_mode": "weekly"
}[
{
"date": "2026-03-21",
"value": 47,
"volume": 25853617,
"keyword": "bitcoin",
"source": "google search"
},
// ... up to 261 weekly data points
]/Get Growth
Calculates point-to-point percentage growth for a keyword over one or more time windows. Supports preset strings ("12M", "YTD", etc.) or exact custom date pairs. Pass one source or a comma-separated list (e.g. amazon, tiktok, youtube) for multi-source comparison.
Quota: 1 request per source + keyword (all percent_growth periods in that call). Full rules
Request body
| Field | Type | Required | Description |
|---|---|---|---|
source | string | Required | One source or comma-separated list. See Data Sources. |
keyword | string | Required | Keyword, brand, or topic. Format depends on source — see Data Sources. |
percent_growth | array | Optional | Preset strings or custom date objects. Defaults to ["12M"] if omitted. |
data_mode | string | Optional | Weekly only — approximately 5 years. Omit when using MCP. |
Growth period presets
7D14D30D1M2M3M6M9M12M1Y18M24M2Y36M3Y48M60M5YMTDQTDYTDCustom date range object
| Field | Type | Description |
|---|---|---|
name | string | Optional label returned in results. |
recent | string | More recent date, YYYY-MM-DD. |
baseline | string | Baseline/comparison date, YYYY-MM-DD. |
Response fields
| Field | Type | Description |
|---|---|---|
search_term | string | The keyword queried. |
data_source | string | The source used. |
results | array | One object per period requested. |
period | string | Period identifier, e.g. "12M" or custom name. |
growth | number | Percentage change, positive or negative. |
direction | string | "increase" or "decrease". |
recent_date | string | ISO 8601 date of the recent data point. |
baseline_date | string | ISO 8601 date of the baseline point. |
recent_value | number | Normalized score at the recent date. |
baseline_value | number | Normalized score at the baseline date. |
volume_available | boolean | Whether absolute volume exists for this source. |
recent_volume | number | null | Absolute volume at the recent date. |
baseline_volume | number | null | Absolute volume at the baseline date. |
volume_growth | number | null | Volume growth %, if available. |
metadata | object | total_data_points, calculations_completed, all_successful. |
{
"source": "google search",
"keyword": "nike",
"percent_growth": ["12M", "3M", "YTD"]
}{
"source": "amazon",
"keyword": "nike",
"percent_growth": [
{
"name": "Last Year",
"recent": "2025-12-31",
"baseline": "2024-12-31"
}
]
}{
"search_term": "nike",
"data_source": "google search",
"results": [
{
"period": "12M",
"growth": -12.31,
"direction": "decrease",
"recent_date": "2026-03-21",
"baseline_date": "2025-03-22",
"recent_value": 57,
"baseline_value": 65,
"volume_available": true,
"recent_volume": 24158298,
"baseline_volume": 27548936,
"volume_growth": -12.31
}
],
"metadata": {
"total_data_points": 261,
"calculations_completed": 1,
"all_successful": true
}
}/Get Top Trends
Returns ranked items from live platform feeds stored for Trends MCP. On the REST API, omit type to aggregate every feed in one response (same semantics the handler uses internally). On MCP, the get_top_trends tool requires an explicit type per call. There is no single MCP invocation that returns all feeds at once.
Quota: per feed (type) and per page (limit / offset). Full rules
Request body
| Field | Type | Default | Description |
|---|---|---|---|
mode | string | Set to "top_trends". | |
type | string | all (REST) | REST: optional; omit for all feeds. MCP: required (one feed per tool call). |
category | string | Optional filter for Amazon Best Sellers by Category and Top Websites only. | |
limit | integer | 25 | Max items per feed (up to 200). |
offset | integer | 0 | REST: skip this many rows per feed for pagination (when the backend supports it for that feed). |
Available feeds
Amazon Best Sellers by CategoryAmazon Best Sellers Top RatedApp Store Top FreeApp Store Top PaidGitHub Trending ReposGoogle News Top NewsGoogle PlayGoogle TrendsIMDb MOVIEmeterOpen Library Trending BooksReddit Hot PostsReddit World NewsSteam Most PlayedTop WebsitesSpotify Top PodcastsTikTok Trending HashtagsWikipedia TrendingX (Twitter) TrendingYouTube Trending{
"mode": "top_trends",
"type": "Google Trends",
"limit": 10
}{
"as_of_ts": "2026-03-26T22:22:25Z",
"type": "Google Trends",
"limit": 10,
"count": 10,
"data": [
[1, "chuck norris"],
[2, "project hail mary"],
[3, "bachelorette cancelled"]
// ... [rank, name] pairs
]
}MCP / AI
AI Prompts
When using Trends MCP through an AI assistant (Claude, ChatGPT, Cursor, etc.), include "using TrendsMCP" or "via TrendsMCP" in your prompt so the AI routes to the MCP instead of a web search.
nvidia over the past 5 years."com.openai.chatgpt."Stanley cup."Bitcoin weekly."air fryer over 5 years."langchain weekly."Elden Ring."Tesla over the last year."wallstreetbets on Reddit."GLP-1 grown over the past 12 months?"Anthropic on Google Search."Duolingo?"weight loss drugs across Google, TikTok, and Amazon."Meta changed over the past 6 months?"AI agents from Jan 2025 to Jan 2026."wallstreetbets on Reddit over the last 30 days?"running shoes."Electronics."Live leaderboards: MCP tools require one feed (type) per call. The REST Get Top Trends request can omit type to return every feed in one response.
Errors
Errors return JSON with an error string and message. HTTP status may be 4xx/5xx depending on the failure; some upstream gaps are reported as data_unavailable (or similar) with a generic message rather than not_found.
| Status | Error code | Meaning |
|---|---|---|
| 400 | missing_parameter | Required field missing from request body |
| 400 | invalid_source | Unrecognized source value (message may list allowed values) |
| 401 | Missing or invalid API key | |
| 404 | not_found | No series or entity matched this keyword/source (when the pipeline classifies it that way) |
| varies | data_unavailable | Pipeline could not return data (temporary gap, unsupported query, or empty upstream). HTTP status is not always 404; read message. |
| 429 | rate_limited | Monthly request limit reached. Upgrade for more. |
| 500 | internal_error | Unexpected server error |
Additional codes can appear as the data layer evolves; treat message as the operator-facing detail.
{
"error": "missing_parameter",
"message": "The 'keyword' parameter is required."
}