Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Steam market intelligence MCP server for game developers: app search, trends, reviews, news.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
STEAM_MCP_BACKEND_URL, STEAM_MCP_AUTO_UPDATE, STEAM_MCP_UPDATE_ORIGINYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"steam": {
"command": "uvx",
"args": [
"playtide-steam-mcp"
],
"env": {
"STEAM_MCP_BACKEND_URL": "your-value",
"STEAM_MCP_AUTO_UPDATE": "your-value",
"STEAM_MCP_UPDATE_ORIGIN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add steam --env STEAM_MCP_BACKEND_URL=your-value --env STEAM_MCP_AUTO_UPDATE=your-value --env STEAM_MCP_UPDATE_ORIGIN=your-value -- uvx playtide-steam-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"steam": {
"command": "uvx",
"args": [
"playtide-steam-mcp"
],
"env": {
"STEAM_MCP_BACKEND_URL": "your-value",
"STEAM_MCP_AUTO_UPDATE": "your-value",
"STEAM_MCP_UPDATE_ORIGIN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"steam": {
"type": "stdio",
"command": "uvx",
"args": [
"playtide-steam-mcp"
],
"env": {
"STEAM_MCP_BACKEND_URL": "your-value",
"STEAM_MCP_AUTO_UPDATE": "your-value",
"STEAM_MCP_UPDATE_ORIGIN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
STEAM_MCP_BACKEND_URL envSTEAM_MCP_AUTO_UPDATE envSTEAM_MCP_UPDATE_ORIGIN envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Playtide-studios, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.8) reached the registry 25 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Steam market intelligence for AI agents — an MCP server that gives your coding assistant live Steam data: app search, player-count trends, store details, review mining, and news digests.
Built for game developers and community managers who want Steam answers inside their IDE conversation instead of tab-switching to store pages.
Steam's public APIs are fragmented (store search, appdetails, user stats) and none of them keep player-count history — the single most useful signal for launch planning. steam-mcp stitches the surfaces together behind one tool set and pairs them with a companion backend that snapshots player counts every 30 minutes, so your agent can answer "how is the game actually doing" with real numbers.
# from PyPI
pip install playtide-steam-mcp steam-mcp
or from source:
git clone https://github.com/Playtide-studios/steam-mcp.git
cd steam-mcp npm install npm start
Requires Node 26+. Zero runtime dependencies — the server talks plain HTTP/JSON-RPC over stdio.
| Tool | What it does |
|---|---|
steam_search_apps | Resolve a game name to appids via Steam store search |
steam_get_app_overview | One-call health check: players, reviews, price, release, genres, latest news |
steam_get_store_details | Full store listing: pricing per region, platforms, DLC count, metacritic |
steam_get_app_reviews | Review mining with recency/sentiment/keyword filters + representative quotes |
steam_get_game_news | News and patch-note digests, summary or full text |
steam_get_player_trend | Player-count history with min/max/avg, week-over-week change, and a plain-language insight line |
steam_get_market_pulse | Curated market digest for game developers: Steam trends, live-ops patterns, competitor notes |
stdio (Claude Desktop / Cursor / any MCP client):
{
"mcpServers": { "steam": { "command": "node", "args": ["/path/to/steam-mcp/src/index.ts"] } } }
Streamable HTTP:
npm run start:http # serves MCP on http://localhost:8788/mcp
Ready-to-edit client configs live in examples/.
| Variable | Default | Purpose |
|---|---|---|
STEAM_MCP_BACKEND_URL | https://api.playtide.dev | Companion backend base URL — hosted beta by default; override to self-host. Must be https:// unless loopback |
STEAM_MCP_BACKEND_KEY | — | Backend API key (optional; the hosted beta is open) |
STEAM_MCP_REMOTE_MANIFEST | 0 | Opt in to fetching tool descriptions from the backend each boot |
STEAM_MCP_TIMEOUT_MS | 10000 | Per-request timeout to Steam or the backend |
Everything else is zero-config: tool schemas are pinned to the packaged manifest (see src/fallback-manifest.json).
Trend and pulse data come from the steam-mcp companion backend — a small Express + Postgres service that snapshots player counts for every tracked app every 30 minutes.
https://api.playtide.dev out of the box; no key needed during beta. To pin it explicitly: STEAM_MCP_BACKEND_URL=https://api.playtide.dev npm start
STEAM_MCP_BACKEND_URL to your instance. See docs/TROUBLESHOOTING.md for connectivity help.Backend unreachable, HTTPS requirement errors, deprecated_client on trend calls, rate limits — see docs/TROUBLESHOOTING.md.
Issues and PRs are welcome — see CONTRIBUTING.md. Bug reports that include the failing tool call JSON get fixed first.
MIT © Playtide Studios. Steam is a trademark of Valve Corporation; this project is not affiliated with Valve.