The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Steam Reviews MCP listing page.
Give your AI assistant access to Steam reviews, game details, patch notes, and community discussions. This MCP server reads public Steam data. No API key or Steam login is needed.
Once connected, try asking:
Use a current Node.js LTS release. Node.js 24 or newer is recommended.
Your MCP client can start the server with npx, so there is no separate install step.
For Claude Desktop, add this entry to claude_desktop_config.json:
The config file is at:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonRestart Claude Desktop after saving. For other MCP clients, use the same command and arguments with the stdio transport in that client's configuration format.
The container starts in HTTP mode:
Connect an SSE-capable MCP client to http://localhost:8086/mcp.
Choose SSE as the transport, rather than Streamable HTTP.
For Docker Compose:
Check that the server is running with curl http://localhost:8086/health.
Your assistant handles the tool arguments. Ask for a country, language, date range, or topic in your question.
| Tool | What it does |
|---|---|
search_steam_games | Find games by name. |
get_game_info | Get regional prices, review scores, Steam Deck ratings, requirements, and Store details. |
fetch_reviews | Read player reviews with filters for date, language, and recommendation. |
analyze_reviews | Summarize a review sample, with themes and linked quotes. |
fetch_app_announcements | Read official app announcements, patch notes, and hotfixes. |
search_app_discussions | Search a game's public community discussions. |
fetch_discussion_thread | Read a discussion thread and its replies. |
Review summaries cover a sample, and discussion threads are read one page at a time. Community posts reflect player claims, not official announcements. The discussion tools and Steam Deck review filter are experimental and may not always return results.
These environment variables are optional. Set them in your MCP client's server
environment or pass them to Docker with -e.
| Variable | Default | Purpose |
|---|---|---|
CACHE_ENABLED | true | Cache Steam responses. |
CACHE_MAX_SIZE | 1000 | Maximum cached entries. |
RATE_LIMIT_ENABLED | true | Limit outgoing Steam requests. |
MAX_REQUESTS_PER_MINUTE | 30 | Request limit. |
HTTP_MODE | false | Use HTTP/SSE instead of stdio. The Docker image sets this to true. |
PORT | 8086 | HTTP listening port. |
If your client cannot start the server, check node --version and confirm it can
find npx. The stdio server writes logs to stderr and reserves stdout for MCP
messages. You do not need to set DOTENV_CONFIG_QUIET.
For Docker, check docker logs steam-reviews-mcp and the /health endpoint.
If health succeeds but the MCP client cannot connect, check that it supports SSE
and uses /mcp.
Steam timeouts and HTTP 429 responses can mean requests are being rate-limited.
Keep caching enabled and reduce MAX_REQUESTS_PER_MINUTE if these persist.
npm test builds the server and runs offline tests. To run the built server over
stdio, use node build/index.js. See
CONTRIBUTING.md
for contribution guidelines and
CHANGELOG.md
for release history.
Licensed under MIT. You can support the project via PayPal.