Steam Trends API

What Steam Trends API MCP server does

The Steam Trends API MCP server provides access to Steam player-interest data through Trends API operations. It supports three main jobs: retrieving a monthly time series for a game, measuring growth over one or more periods, and reading a live most-played feed.

Historical requests accept a game display name such as counter-strike 2. The backend resolves that name through Steam store search; AppIDs are not request parameters. Time-series values are normalized from 0 to 100 for the selected title, rather than being raw concurrent-player counts. A returned point includes a date and value, with volume and source metadata available when supplied.

Growth requests can use standard windows such as 7D, 30D, 3M, 12M, YTD, or 5Y, and can also define a custom recent and baseline date. Multiple windows can be requested in one API call.

How it works

The client sends authenticated requests to POST https://api.trendsapi.ai/api with a bearer token. Historical operations use source: "steam" and either the get_time_series or get_growth mode. Live rankings use the get_top_trends mode with the exact feed type Steam Most Played.

The Python package exposes synchronous and asynchronous clients. Synchronous methods return typed objects such as TrendsDataPoint and GetGrowthResponse; asynchronous methods can be awaited concurrently. Results can also be converted into a pandas DataFrame for date parsing and resampling.

The Steam Trends API MCP server is suited to questions about how interest in a named Steam game has changed, comparisons across defined growth periods, and current ranking snapshots. It is less suitable when raw Steam concurrent-user counts are required.

Setup and configuration

Install the Python package with pip install trendsapi-steam and provide the TRENDSAPI_KEY environment variable. The same key is used by the Trends API HTTP service and can alternatively be passed directly to the Python client. Python 3.9 or newer is required.

A direct HTTP request uses the Authorization: Bearer $TRENDSAPI_KEY header and JSON content. The server-side API returns an HTTP body containing JSON; the SDK decodes that payload for callers. A free key is available from the Trends API website.

Tools and capabilities

• Retrieve monthly Steam trend points with get_time_series.
• Calculate growth for preset or custom date windows with get_growth.
• Read ranked live results with get_live.
• Call the top-trends operation directly with get_top_trends.
• Request multiple growth windows in one request.
• Use synchronous or asynchronous Python clients.

Limitations and notes

Steam history is monthly, and its value field is an index relative to the selected title, not an absolute CCU measurement. The request must use lowercase source: "steam"; using type: steam is invalid, while the live feed requires the exact type Steam Most Played.

A 404 means no series was found for the supplied keyword and should not be retried. A 401 indicates an invalid or missing key, and a 429 indicates quota exhaustion. Client libraries retry 5xx responses before raising an error. Each successful asynchronous operation counts as one billed request.

The Steam Trends API MCP server accepts game names rather than AppIDs. Live responses include a snapshot timestamp, pagination fields, and [rank, label] rows. The optional category parameter is documented for Amazon Best Sellers by Category and Top Websites feeds, not the Steam feed.