Skip to main content
Glama
deenesjakoruzh
trendsmcp-ai

steam-trends-mcp

by trendsmcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam-trends-mcp

Steam 趋势 MCP 兼容 Claude 兼容 Cursor

面向 AI 助手的 Steam 玩家趋势数据 追踪 Steam 上任何游戏的实时在线玩家数量和游戏热度。玩家趋势数据能够揭示哪些游戏正在增长、哪些正在下滑，以及大型发布或更新何时推动数据飙升。

完整文档和在线演示： https://trendsmcp.ai/steam-trends

属于 Trends MCP 的一部分——提供 12+ 数据源实时趋势的 MCP 服务器。 查看主仓库：https://github.com/trendsmcp/trends-mcp

两步快速上手

第 1 步： 在 trendsmcp.ai 免费获取 API 密钥 每日 100 次请求，无需信用卡。

第 2 步： 添加到你的 AI 客户端（替换 YOUR_API_KEY）：

+ 添加到 Cursor（一键安装）

Cursor / Windsurf / Cline   (~/.cursor/mcp.json 或等效文件)

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

VS Code / GitHub Copilot   (.vscode/mcp.json)

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

Claude Desktop   (claude_desktop_config.json) 用户 → 设置 → 开发者 → 编辑配置 —— 在 mcpServers 内添加

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

Claude.ai（浏览器）   设置 -> 连接器 -> 添加自定义连接器：

https://api.trendsmcp.ai/mcp

Related MCP server: Steam Review and Forum MCP

示例查询

连接后，向 AI 提问：

get_trends(keyword='Counter-Strike 2', source='steam', data_mode='weekly')

可用工具

工具

功能说明

get_trends

获取该数据源中某个关键词的时间序列数据

get_growth

获取 1 周、1 个月、3 个月、6 个月、1 年周期的增长率

get_top_trends

获取该数据源当前的流行趋势

get_ranked_trends

按热度排名获取热门话题

常见问题

Trends MCP 返回哪些 Steam 数据？

返回 Steam 上任何游戏的标准化同时在线玩家数量趋势（0-100 分制）。提供周度时间序列、增长率以及最高玩家数据。对于追踪游戏在发布、更新或促销活动前后的热度变化非常有用。

如何在查询中指定游戏？

使用游戏在 Steam 上显示的名称——例如 'Counter-Strike 2'、'Palworld' 或 'Elden Ring'。MCP 服务器会自动将名称解析为对应的 Steam 应用 ID。

什么是同时在线玩家数？

由 Steam 追踪的同时在游戏中的玩家数量。最高同时在线玩家数（PCU）是衡量游戏人气和实时参与度的标准指标。

对投资或市场研究有何帮助？

游戏工作室、投资者和分析师利用 Steam 玩家趋势来评估一款游戏的商业热度，及早发现爆款游戏，并追踪游戏在时间上的玩家留存情况。

数据能回溯多远？

最多提供 5 年的周度数据，让你能够获取 Steam 上任何游戏的完整发布历史、季节性周期和长期留存趋势。

所有数据源

Trends MCP 一次连接覆盖 12+ 数据源： Google 搜索、YouTube、TikTok、Reddit、亚马逊、维基百科、 新闻情感分析、网站流量、应用下载、Steam、npm 等。

浏览全部：https://trendsmcp.ai/data-sources

也可作为 Python 客户端使用

同一 API 密钥可直接在 Python 中使用 —— 无需 MCP 主机。

pip install steam-trends-mcp
import os
from steam_trends_mcp import TrendsMcpClient, SOURCE

client = TrendsMcpClient(api_key=os.environ["TRENDSMCP_API_KEY"])

series  = client.get_trends(source=SOURCE, keyword="your keyword")
growth  = client.get_growth(source=SOURCE, keyword="your keyword", percent_growth=["1M", "3M", "12M"])
top     = client.get_top_trends(type="Steam", limit=10)

完整 Python 文档：trendsmcp.ai/docs

许可证

MIT © Trends MCP

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
NameRequiredDescriptionDefault
sourceYesOne 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'.
keywordYesWhat 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_growthNoGrowth 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
NameRequiredDescription
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint, openWorldHint, and idempotentHint annotations, the description adds useful behavioral context: values are on a 0-100 scale with absolute volume when available, and the agent should tell the user their plan limit is reached on rate limiting or quota exhaustion. These details are not present in the structured fields and do not contradict the annotations.

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 every sentence earns its place: core operation, output scale, sibling preference, app-source caveat, and rate-limit handling. It front-loads the primary purpose and avoids redundant phrasing.

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?

With a detailed input schema, an output schema, and safety annotations, the description fills the remaining gaps: tool selection, output scale, source disambiguation, and error behavior. It is complete enough for an agent to invoke the tool correctly without further inference.

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?

The input schema already documents all parameters thoroughly, including valid sources, keyword formatting rules per source, and every preset growth window. The description references preset windows and Android bundle IDs but does not add meaning beyond the schema, so a baseline of 3 is appropriate.

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 opens with a specific action and resource: 'Point-to-point growth for a keyword on one or more sources.' It also names sibling tools to disambiguate itself, stating it is preferred over get_time_series for growth questions and clarifying that app sources are 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?

It gives an explicit selection rule: 'Prefer this over get_time_series for growth questions.' It also warns against confusing app downloads/app rankings with get_top_trends live boards, and specifies how to handle rate limits or quota exhaustion. This gives the agent clear when-to-use and when-not-to-use guidance.

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
NameRequiredDescriptionDefault
sourceYesExactly 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'.
keywordYesWhat 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
NameRequiredDescription
resultYes

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.7
    • First observedget_growth
    • First observedget_time_series
    • First observedget_top_trends
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.7/5.0

Scored across 3 tools

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

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Steam Review and Forum MCP

    icue
    A
    license
    A
    quality
    C
    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.
    13
    398 npm
    1
    BSD 3-Clause

  • Steam Trends API MCP Server

    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.
    MIT
  • aggrometer by Aggrometer

    aggrometerofficial

    Aggrometer
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables querying live cross-platform gaming market data — Steam players, Twitch/YouTube viewership, prices, discounts, hype, and the aggro metric — through 8 read-only tools for summaries, rankings, genre rollups, game details, and search.
    MIT