SEO Trends MCP

You: Using TrendsMCP, compare 6-month growth for GLP-1 on Google, TikTok, and Amazon.
Agent: Google Search  +84%       TikTok         +212%       Amazon         +61%

Three tools. Normalized 0–100 where the pipeline supports it. No per-platform keys. No scraping on your side.

Quick install

Same four clients as the site hero. Get a free key first (100 req/mo). Claude and ChatGPT sign you in with OAuth. Cursor and VS Code: click, then put your key from /account if the deeplink used a placeholder.

[Add to Claude] [Add to Cursor] [Add to ChatGPT] [Add to VS Code]

Then ask: Using TrendsMCP, what's trending on Google right now?

Tools · Sources · Feeds · REST · Install in other clients

What this is

Hosted MCP at https://api.trendsmcp.ai/mcp. Same Bearer key for POST https://api.trendsmcp.ai/api. This repo also has a stdio adapter for Glama and local hosts.

Install in other clients

Replace YOUR_API_KEY with the key from your account.

claude mcp add --scope user --transport http trends-mcp https://api.trendsmcp.ai/mcp \  --header "Authorization: Bearer YOUR_API_KEY"

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

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

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

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

{  "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" }    }  }}

pip install -e .python -m trends_mcp_server

{  "mcpServers": {    "trends-mcp": {      "command": "python",      "args": ["-m", "trends_mcp_server"],      "env": { "TRENDSMCP_API_KEY": "YOUR_API_KEY" }    }  }}

Tools

Always-current parameter lists: docs.

get_time_series

Weekly (or daily) history for one source + keyword. Same name on MCP and REST (mode: "get_time_series"). REST also accepts get_trends as an alias.

Index is 0–100 where the pipeline supports it (100 = peak in the returned window). volume is present when that source has an absolute series.

get_growth

Point-to-point percent change. Several windows in one call still count as one request for that source + keyword.

Presets: 7D 14D 30D 1M 2M 3M 6M 9M 12M 1Y 18M 24M 2Y 36M 3Y 48M 60M 5Y MTD QTD YTD.

get_top_trends

Live ranked list. No keyword. On MCP, type is required and must match the feed name exactly (including capitals). On REST, omit type only if you intend to pull every feed (billed per feed).

Prompts that route correctly

Using TrendsMCP, what's trending on Google right now?Using TrendsMCP, what are the hottest Reddit posts right now?Using TrendsMCP, compare 6-month growth for creatine gummies on Google, TikTok, and Amazon.Using TrendsMCP, show Google Search history for protein soda.Via TrendsMCP, pull npm download history for langchain.Using TrendsMCP, show Steam concurrent players for Elden Ring.Via TrendsMCP, Android downloads for com.openai.chatgpt.Using TrendsMCP, fastest-climbing Amazon best sellers in Toys Games this week.

Keyword sources

source on get_time_series / get_growth. Not the same strings as type on live feeds.

source: "Google Trends" is invalid. Use google search for history and type: "Google Trends" for the live board.

Live feeds

type on get_top_trends. Copy the name exactly.

Category name lists: docs.

iOS charts, GitHub repos, Spotify, IMDb, Open Library, Substack, and Top Websites are feeds, not source values. There is no source: "web traffic".

REST API

curl -sS -X POST https://api.trendsmcp.ai/api \  -H "Authorization: Bearer $TRENDSMCP_API_KEY" \  -H "Content-Type: application/json" \  -d '{"mode":"get_top_trends","type":"Google Trends","limit":5}'

import os, requests
r = requests.post(    "https://api.trendsmcp.ai/api",    headers={"Authorization": f"Bearer {os.environ['TRENDSMCP_API_KEY']}"},    json={"mode": "get_growth", "source": "google search", "keyword": "bitcoin", "percent_growth": ["3M", "12M"]},)print(r.json())

Python client: pip install trendsmcp.

Limits and errors

Annual billing is 20% less. Same source catalog on every plan. Free history and “top N” caps are on pricing. Failed calls are not billed. Over quota returns 429 / rate_limited (no surprise overages).

One billed request:

• get_time_series: one source + keyword
• get_growth: one source + keyword (all windows in that call included)
• get_top_trends: per type (and pagination as documented)

Do not commit keys. Claude.ai connectors use OAuth; other clients use Authorization: Bearer ….

What this does not do

• Region / geo breakdown, related queries, or related topics
• Hourly series
• get_time_series across several sources in one call (use get_growth with a comma-separated source list, or several get_time_series calls)
• Inventing feed names: MCP type must match the table

Develop this repo

pip install -e .python -m trends_mcp_server

CI: .github/workflows/ci.yml. Security: SECURITY.md. Issues: github.com/trendsmcp-ai/Trends-MCP/issues.

Links

• Account / key
• Docs
• Pricing
• llms.txt
• TrendWatch (alerts in your own GitHub repo)

MIT © Trends MCP