SteamStats MCP Server

What is SteamStats MCP Server?

The SteamStats MCP Server is a Python-based Model Context Protocol (MCP) server that acts as an intermediary between an MCP client (like Roo) and the Steam Web API, providing structured access to Steam game statistics and user information. It is built with FastAPI and exposes a single /message endpoint that accepts JSON-RPC style tools/call requests. Note: The README explicitly warns that the current implementation is not operational.

How to use SteamStats MCP Server?

Clone the repository, install dependencies using UV, set the required STEAM_API_KEY environment variable, and optionally configure LOG_LEVEL, HOST, and PORT. Run the server with uvicorn main:app --host $HOST --port $PORT --reload. Connect an MCP client by configuring its mcp.json file with the sse type pointing to http://<HOST>:<PORT>/message.

Key features of SteamStats MCP Server

• Acts as an intermediary between MCP clients and the Steam Web API.
• Exposes a single /message endpoint for JSON-RPC tools/call requests.
• Validates requests using Pydantic models.
• Supports multiple Steam API commands (e.g., getCurrentPlayers, getAppDetails).
• Configurable logging, host, and port via environment variables.
• Uses Server-Sent Events (SSE) transport for MCP client connections.

Use cases of SteamStats MCP Server

• Querying the current number of players for a specific Steam game.
• Retrieving detailed information about a Steam application.
• Fetching player achievements and user stats for a game.
• Getting global achievement percentages and game news.
• Listing all supported Steam Web API endpoints.

FAQ from SteamStats MCP Server

Is the SteamStats MCP Server currently operational?

No. The README explicitly states: "Current implementation is not operational!"

What are the runtime dependencies for SteamStats MCP Server?

The server requires Python 3.11+, the UV package manager, FastAPI, Pydantic, Uvicorn, and the Requests library. A Steam Web API key (obtainable from the Steam Developer website) is mandatory.

How do I configure the SteamStats MCP Server?

Configure via environment variables: STEAM_API_KEY (required), LOG_LEVEL (optional, defaults to INFO), HOST (optional, defaults to 0.0.0.0), and PORT (optional, defaults to 8000).

What transport protocol does SteamStats MCP Server use for MCP client connections?

The server communicates with MCP clients over HTTP using Server-Sent Events (SSE). The client must configure its mcp.json file with type "sse" and the server's /message URL.

Where does the SteamStats MCP Server data come from?

All data is fetched from the Steam Web API (e.g., ISteamUserStats, ISteamNews, etc.). The server does not store any data locally; it processes API responses and returns them to the client.