Steam MCP

A read-only Model Context Protocol server for the public Steam Web API and storefront — 41 tools, 5 prompts, and 2 resources that let any MCP client (Claude Desktop, Claude Code, Cursor, …) answer questions about Steam: your friends, games, playtime, and achievements, plus account-independent things like sales, reviews, live player counts, Steam Deck compatibility, discovery, recommendations, and co-op planning.

Read-only · official Steam APIs only · open source. Nobody logs in, and the server never writes, trades, posts, launches games, or makes purchases.

Quick start — no API key needed

Install uv, then:

Claude Code

claude mcp add steam -- uvx steam-mcp

That's the whole setup. 19 of the 41 tools work with no credential at all — anything about the store or a game itself:

"Is Baldur's Gate 3 worth buying, and how are its recent reviews trending?" "What co-op games are on sale under £20 right now?" "How many people are playing Helldivers 2 this minute?" "Will Hades II run properly on my Steam Deck?"

The three game-finders (steam_discover, steam_should_i_buy, steam_recommend) work without a key too, as long as you don't personalize them.

Adding your own account

A free Steam Web API key (a minute to get) unlocks the other 22 — the ones that read a specific account: library, playtime, friends, achievements, wishlist, inventory. Add STEAM_USER too and "my"/"I" default to you, so you never have to paste a SteamID:

claude mcp add steam --env STEAM_API_KEY=YOUR_KEY --env STEAM_USER=your_steam_name -- uvx steam-mcp

Tip: this defaults to the current project. Add --scope user only if you want Steam in every project — that keeps its tools in context everywhere, so prefer per-project scope unless Steam is cross-cutting for you.

Claude Desktop — download steam-mcp.mcpb from the latest release and open it (Settings → Extensions). Both fields are optional; leave them blank for the keyless tools and fill them in later.

Cursor / Cline / Windsurf and the manual pip setup are under Setup below.

Without a key, the account tools are still listed but marked [unavailable: needs STEAM_API_KEY], so your assistant knows to reach for a keyless tool instead of failing at one it can't use.

What it can answer

Account / profile (needs a public profile; set STEAM_USER and "my"/"I" default to you — no SteamID needed):

• "Who's on my friends list, and who's online right now?"
• "Which of my friends own Helldivers 2 — and who's playing it now?"
• "It's game night — what co-op games do my online friends and I all own?"
• "Analyze my library — my backlog, and what I loved but abandoned."
• "Which achievements am I missing in Hollow Knight, and which are my rarest?"
• "What's on my wishlist, and is any of it on sale?"
• "Based on what I play most, what should I check out next?"
• "What's in my CS2 inventory, and which items are marketable?"

Account-independent (works for any game, no SteamID needed):

• "Is Baldur's Gate 3 worth buying — and how are its recent reviews trending?"
• "What's on sale right now, and what are the current top sellers?"
• "How many people are playing Counter-Strike 2 this minute?"
• "Will Hades II run on my Steam Deck?"
• "What's the Community Market price of a Field-Tested AK-47 | Redline?"
• "Is Elden Ring a soulslike? What are its community tags?"
• "Find well-reviewed co-op roguelikes under $20."
• "Recommend games like Hollow Knight that I don't already own."

Tools

Every tool supports response_format: "markdown" (default) or "json", and all are annotated readOnlyHint: true. Prefer the composite tools (steam_should_i_buy, steam_recommend, steam_discover, steam_plan_coop_night) over chaining several calls, and ask for json only when you need to parse fields. Tools that read localized text accept a language parameter — a Steam language name like french or schinese (default english).

* steam_discover, steam_should_i_buy, and steam_recommend need no key for the store data; their personalization (passing a steamid to use a user's library/taste) requires a key and a public profile.

† steam_get_inventory reads a keyless endpoint, but it still has to know whose inventory — and turning a vanity name (or STEAM_USER) into a SteamID64 is itself a keyed call. Pass a raw 17-digit SteamID64 and it works with no key.

Prompts & resources

Beyond tools, the server ships prompts (guided one-click flows that orchestrate the tools) and resources (reference Steam entities by URI):