Which integrations are available for this server?

Provides trend data (time-series, growth rates, top trends) for Amazon products or search terms. Provides trend data (time-series, growth rates, top trends) from Google Search. Provides trend data (time-series, growth rates, top trends) for npm packages. Provides trend data (time-series, growth rates, top trends) from Reddit. Provides player trend data for any game on Steam, including concurrent player counts, growth rates, and weekly time series. Provides trend data (time-series, growth rates, top trends) from TikTok. Provides trend data (time-series, growth rates, top trends) from Wikipedia page views. Provides trend data (time-series, growth rates, top trends) from YouTube.

How do I use steam-trends-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@steam-trends-mcp What are the current player trends for Elden Ring?" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

steam-trends-mcp

by trendsmcp-ai

Overview Schema Source Related Servers Score Discussions

Python

Remote

Steam Trends MCP

Live trend data for AI agents. Google, TikTok, YouTube, Amazon, Reddit, and 30+ other sources. One MCP connection, one API key.

PyPI License: MIT MCP Free tier Glama

Get a free API key · Docs · Pricing · Data sources · PyPI · Glama

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.

Client	After you click
Claude	Connector name and URL are prefilled (`https://www.trendsmcp.ai/mcp`). Confirm, then authorize.
Cursor	Approve the MCP install. Replace `YOUR_API_KEY` if prompted.
ChatGPT	Enable Developer mode (Profile → Settings → Security). Name `Trends MCP`, URL `https://www.trendsmcp.ai/mcp`, then authorize.
VS Code	Sign in on the account page and use the VS Code button so the key is included.

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

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

Related MCP server: steam-trends-mcp

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.

Tool	Use when	Needs a keyword?
`get_time_series`	History for one keyword on one source	Yes
`get_growth`	Percent change over 7D–5Y (several windows in one call)	Yes
`get_top_trends`	What is ranking on a platform right now	No

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"

~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json)

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

.vscode/mcp.json or Command Palette → MCP: Add Server. Prefer the account-page VS Code button so the key is wired for you.

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

Uses serverUrl, not Cursor’s url + transport. File: ~/.codeium/windsurf/mcp_config.json.

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

Remote server, type exactly streamableHttp. See llms-install.md.

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

Settings → Connectors → add https://www.trendsmcp.ai/mcp. This path uses OAuth on www.trendsmcp.ai. Do not put a Bearer key in that connector config.

Hosted HTTP is still the product default. This process lists tools with no key; paid calls need TRENDSMCP_API_KEY and bill the same quota.

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

Say “using TrendsMCP” so the model picks these tools instead of web search. More clients: docs.

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.

Argument	Required	Notes
`keyword`	yes	Format depends on source (table below)
`source`	yes	One source per call. Lowercase catalog names
`data_mode`	no	REST only. `weekly` (default) or `daily`

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.

Argument	Required	Notes
`keyword`	yes	Same formats as `get_time_series`
`source`	yes	One source, or a comma-separated list (`google search, tiktok, amazon`)
`percent_growth`	no	Default `["12M"]`. Presets below, or `{ "recent", "baseline", "name" }` date objects

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).

Argument	Required on MCP	Notes
`type`	yes	See live feeds
`limit`	no	Default 25, max 200
`offset`	no	Pagination
`category`	for some types	Amazon / Google Trends / Top Websites / Substack / TikTok hashtag category boards
`sort`	no	`rank` (default) or `rank_change`
`window`	no	With `sort=rank_change`: `1d` `3d` `7d` `14d` `30d`

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`	Signal	`keyword`
`google search`	Search volume	Any phrase
`google images`	Image search volume	Any phrase
`google news`	News-tab volume	Any phrase
`google shopping`	Shopping-tab volume	Any phrase
`youtube`	YouTube search volume	Any phrase
`tiktok`	Hashtag volume	Hashtag or topic (`#` optional)
`reddit`	Subreddit attention	Name only, no `r/`
`amazon`	Product search volume	Product or category
`wikipedia`	Page views	Article title or topic
`news volume`	Mention volume	Any phrase
`news sentiment`	News tone	Any phrase
`app downloads`	Android downloads	Play bundle id, e.g. `com.openai.chatgpt`
`app rankings`	Android chart position	Bundle id
`npm`	Weekly downloads	Exact package name (`react`, `@babel/core`)
`steam`	Monthly concurrent players	Game display name (`Elden Ring`)

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.

`type`	Board
`Google Trends`	Google searches now
`Google Trends by Category`	Needs `category` (e.g. `Games`)
`Google News Top News`	Google News stories
`TikTok Trending Hashtags`	Hashtags
`TikTok Trending Hashtags by Category`	Needs `category`
`TikTok Trending Searches`	In-app searches
`YouTube Trending`	Videos
`X (Twitter) Trending`	Topics on X
`Reddit Hot Posts`	Front page
`Reddit World News`	r/worldnews
`Wikipedia Trending`	Most-viewed articles
`Amazon Best Sellers Top Rated`	Top-rated sellers
`Amazon Best Sellers by Category`	Needs `category` (e.g. `Toys Games`)
`App Store Top Free` / `App Store Top Paid`	iOS charts
`Google Play`	Play chart
`Top Websites`	Global traffic rank; optional `category`
`Spotify Top Podcasts`	Podcasts
`Steam Most Played`	Live players
`Substack` / `Substack by Category`	Newsletters
`GitHub`	Daily trending repos
`IMDb MOVIEmeter`	Movie activity
`Open Library Trending Books`	Books

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

Plan	Requests / month	Price
Free	100	$0
Starter	1,000	$19
Pro	5,000	$49
Business	25,000	$199

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)

Status	Meaning
400	Bad or missing `source` / `type` / field
401	Missing or invalid key
404	No series for that keyword + source
429	Monthly cap
500	Upstream or internal error

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/steam-trends-mcp/issues.

Available Tools

3 tools

get_growthA

Read-onlyIdempotent

Inspect

Point-to-point growth for a keyword on one or more sources. Each window is a preset string (12M, 3M, YTD, and the other listed periods). Values are on a 0-100 scale, plus absolute volume when available. Prefer this over get_time_series for growth questions. app downloads and app rankings are keyword sources (Android bundle ID). They are not the App Store / Google Play live boards on get_top_trends. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema

Name	Required	Description
`source`	Yes	One source, or comma-separated sources (e.g. 'amazon, tiktok, youtube'). Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'.
`keyword`	Yes	What to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'nike'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes app downloads or app rankings with other sources, keyword must still be the Android bundle ID.
`percent_growth`	No	Growth windows. Default if omitted: ['12M']. Each item must be a preset string: '7D', '1W', '14D', '2W', '30D', '1M', '2M', '3M', '6M', '9M', '12M', '1Y', '18M', '24M', '2Y', '36M', '3Y', '48M', '4Y', '60M', '5Y', 'MTD', 'QTD', 'YTD'. Every preset is a two-date comparison.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds valuable behavioral context: the 0-100 scale plus absolute volume, the preset-window semantics, the Android bundle ID requirement for app sources, and the rate-limit/quota handling instruction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it opens with the core purpose, then the window/scale behavior, tool-selection guidance, source disambiguation, and an error-handling note. Every sentence carries distinct, necessary information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, output schema, and annotations, the description covers all important gaps: growth scale, window presets, sibling differentiation, source-specific keyword requirements, and rate-limit behavior. Nothing essential for an agent to call the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents all three parameters. The description reinforces the preset-window concept and the Android bundle ID constraint, but adds only marginal semantic value beyond what the detailed schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool computes 'Point-to-point growth for a keyword on one or more sources', which is a specific verb+resource combination. It also differentiates itself from siblings by explicitly saying to prefer it over get_time_series for growth questions and clarifying it is not the live boards on get_top_trends.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing guidance: 'Prefer this over get_time_series for growth questions.' It also clarifies that app downloads and app rankings sources are not the App Store / Google Play live boards covered by get_top_trends, preventing incorrect tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_time_seriesA

Read-onlyIdempotent

Inspect

Full historical series for one keyword and one source (0-100 values, plus volume when available). Use for charting or custom math. Not for live 'what's trending now' boards (use get_top_trends). For most growth questions, use get_growth. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema

Name	Required	Description	Default
`source`	Yes	Exactly one source per request. Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'.
`keyword`	Yes	What to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'tesla'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnlyHint and idempotentHint. The description adds behavioral context beyond those hints: the 0-100 value range, volume availability, and rate-limit/quota handling instructions. This provides useful operational detail that annotations do not convey, though the core safety profile is already covered by hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: purpose and scope, usage routing, and error handling. Front-loaded with the core purpose; no repetition or fluff. The alternative tool routing is included efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a two-parameter tool with a full output schema, the description covers purpose, usage scenarios, alternatives, and error handling. An agent has all necessary information to decide when to call it and what to expect, with no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters have detailed, source-specific descriptions (e.g., keyword format per source, valid source list). The tool description adds no additional parameter meaning beyond restating 'one keyword and one source', so the baseline for full schema coverage applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it returns 'Full historical series for one keyword and one source' with a value range and volume detail. It distinguishes itself from siblings get_top_trends and get_growth by stating what it is not for (live trending, growth questions), making the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Directly states when to use it: 'Use for charting or custom math' and when not to: 'Not for live trending (use get_top_trends)' and 'For most growth questions, use get_growth'. Also provides explicit handling for rate-limited or quota-exhausted requests, which is actionable guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_top_trendsA

Read-onlyIdempotent

Inspect

Live top-trending board for exactly one feed type. No keyword. For 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Top Websites', and 'Substack by Category', always pass category. Default sort is current rank. Use sort='rank_change' for climbers vs a prior snapshot (window 1d, 3d, 7d, 14d, or 30d). App Store Top Free, App Store Top Paid, and Google Play are live store boards, not keyword lookups. For an app's history use get_growth or get_time_series with source app downloads or app rankings and an Android bundle ID. Do not use get_time_series for live boards. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

ParametersJSON Schema

Name	Required	Description	Default
`sort`	No	How to rank the board. 'rank' (default): current leaders. 'rank_change': biggest climbers vs a prior snapshot. Mover rows include rank, keyword, prev_rank, and rank_change.	rank
`type`	Yes	Exactly one live feed. Valid: 'Amazon Best Sellers Top Rated', 'Amazon Best Sellers by Category', 'App Store Top Free', 'App Store Top Paid', 'GitHub', 'Google News Top News', 'Google Play', 'Google Trends', 'Google Trends by Category', 'IMDb MOVIEmeter', 'Open Library Trending Books', 'Reddit Hot Posts', 'Reddit World News', 'Top Websites', 'Spotify Top Podcasts', 'Steam Most Played', 'Substack', 'Substack by Category', 'TikTok Trending Hashtags', 'TikTok Trending Searches', 'Wikipedia Trending', 'X (Twitter) Trending', 'YouTube Trending'.
`limit`	No	Max rows to return. Default 25, min 1, max 200.
`offset`	No	Rows to skip for pagination. Default 0.
`window`	No	Lookback used only when sort is 'rank_change'. One of '1d', '3d', '7d', '14d', '30d'. Default '30d'. Short windows only work on daily feeds; weekly and monthly feeds return a note pointing to a longer window.	30d
`category`	No	Pass this whenever type is 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Top Websites', or 'Substack by Category'. Use the official name. Without it those feeds mix every board. Only omit on a first pull to learn the official names.

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint/idempotentHint, the description adds important behavioral context: rate limits and monthly quota handling, default sort behavior, rank-change snapshot windows, category omission behavior, and feed-type quirks. It discloses how the tool behaves in edge cases, which is exactly the kind of transparency that helps an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: purpose, category rule, sort semantics, alternative tool routing, and rate-limit behavior are all covered in a compact, front-loaded format. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given six parameters, sibling tools, and an output schema, the description covers everything an agent needs: valid feed types, category requirements, sort/window semantics, pagination defaults handled in schema, alternatives, and rate-limit response. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds valuable non-obvious semantics: category is mandatory for four specific feed types and mixing occurs otherwise, and sort='rank_change' compares against a prior snapshot. This goes beyond the schema's own parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states a specific verb and resource: it returns a live top-trending board for exactly one feed type, and explicitly says 'No keyword.' This clearly distinguishes it from sibling tools like get_growth and get_time_series without needing to open the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: pass category for certain feeds, use sort='rank_change' for climbers, and use get_growth or get_time_series for app history. It even warns 'Do not use get_time_series for live boards,' giving clear exclusions and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.7Aug 30, 2026
- First observedget_growth
- First observedget_time_series
- First observedget_top_trends

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.7/5.0

Disambiguation5/5

Each tool targets a distinct query type: get_growth handles point-to-point growth, get_time_series provides full historical series, and get_top_trends returns live top-trending boards. The descriptions explicitly cross-reference when to prefer one tool over another, so there is little risk of misselection.

Naming Consistency5/5

All three tool names follow the same get_<specific_noun> pattern using snake_case. The verb prefix is consistent and the object distinguishes the data shape clearly.

Tool Count5/5

Three tools is within the ideal 3-15 range and each one earns its place by covering a distinct data retrieval mode. No redundant or filler tools exist.

Completeness4/5

The set covers the core needs for this domain: historical series, growth calculations, and live trend boards. A minor gap is that there is no explicit tool for listing available sources or categories, though the descriptions mention them inline.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

Steam Trends API
ai.trendsapi
Steam concurrent player trends for any game over time. Free key at trendsapi.ai
Games & Gamification Open Data Entertainment & Media
1
Trends API
ai.trendsapi
Trend data from Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and more as JSON
Search Open Data Web Scraping
1
Trends MCP
ai.trendsmcp
Trend data from Google Trends, YouTube, TikTok, Reddit, Amazon, Wikipedia, npm, Steam and more
Search Open Data Research & Data
237
gamedatakit A
com.borisinc
Live Steam market data for AI agents: top sellers, deals, player counts. Paid per call via x402.
Games & Gamification E-commerce & Retail
52

Related MCP Servers

Steam Review MCP
Search Games & Gamification Text Summarization
fenxer
A
license
B
quality
D
maintenance
Enables LLMs to retrieve and analyze Steam game reviews, providing access to review statistics, game information, and helping summarize pros and cons of games.
Updated 7 months ago (2026-01-28 03:30 UTC)
1
27
7
MIT
steam-trends-mcp
Games & Gamification Entertainment & Media
trendsmcp-ai
A
license
Not graded
quality
C
maintenance
Track concurrent player counts and game momentum for any title on Steam via AI assistants.
Updated 5 months ago (2026-04-03 12:19 UTC)
1
MIT
Steam Review and Forum MCP
Games & Gamification Text Summarization Search
icue
A
license
Not graded
quality
B
maintenance
Enables exploring Steam store reviews and community discussion threads with server-side filtering, temporal analysis, and metadata context for understanding player sentiment and feedback beyond store page noise.
Updated 2 months ago (2026-07-02 03:46 UTC)
29
1
BSD 3-Clause
Steam Trends API MCP Server
Games & Gamification Search Open Data
trendsapi
A
license
Not graded
quality
C
maintenance
Provides Steam concurrent player trends as JSON, offering monthly player time series, growth rates across 3M/6M/12M/5Y windows, and live most-played feeds via a single REST endpoint, without needing a Steam Web API key.
Updated a month ago (2026-08-03 14:05 UTC)
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/trendsmcp-ai/steam-trends-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Steam Trends MCP

Quick install

What this is

Install in other clients

Tools

get_time_series

get_growth

get_top_trends

Prompts that route correctly

Keyword sources

Live feeds

REST API

Limits and errors

What this does not do

Develop this repo

Links

Available Tools

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

`get_time_series`

`get_growth`

`get_top_trends`