Skip to main content
Glama

steam-mcp

steam-mcp MCP server

A local Model Context Protocol (MCP) server that connects Claude to your Steam library. Ask natural-language questions about your games without ever touching the API yourself.

steam-mcp MCP server

"What have I been playing lately?"
"Suggest something from my backlog I haven't touched yet."
"How many hours have I put into RPGs?"
"Tell me about Elden Ring."

Tools

Tool

What it does

get_library

Your full game library — title, playtime, last played

get_recently_played

Games played in the last 2 weeks

search_library

Filter by name, playtime range, or unplayed status

get_game_details

Store metadata — genres, tags, Metacritic score, price

refresh_library

Clear the cache to fetch fresh data from Steam


Related MCP server: steam-mcp

Requirements

  • Node.js 18+

  • A Steam account with a public profile and library

  • A Steam Web API key (free, takes 30 seconds to get)


Setup

1. Get a Steam API key

Go to steamcommunity.com/dev/apikey, log in, and register a key. The domain field can be anything (e.g., localhost).

2. Find your Steam ID

You need either:

  • Your vanity URL username — the custom part of your profile URL: steamcommunity.com/id/YOUR_USERNAME

  • Your 64-bit Steam ID — find it at steamid.io if you don't have a vanity URL

3. Make your profile public

In Steam: your profile → Edit Profile → Privacy Settings → set My Profile and Game details to Public.

4. Run setup

npx steam-mcp setup

This validates your credentials and writes the Claude Desktop config automatically. Restart Claude Desktop when it's done.

Find your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add to the mcpServers section:

{
  "mcpServers": {
    "steam-mcp": {
      "command": "npx",
      "args": ["-y", "steam-mcp"],
      "env": {
        "STEAM_API_KEY": "your_api_key_here",
        "STEAM_ID": "your_vanity_url_or_64bit_id"
      }
    }
  }
}

Local development

git clone https://github.com/jkiley129/steam-mcp.git
cd steam-mcp
npm install
cp .env.example .env
# Edit .env with your API key and Steam ID
npm run build

To use the local build with Claude Desktop, point the config at the built file:

{
  "mcpServers": {
    "steam": {
      "command": "node",
      "args": ["/absolute/path/to/steam-mcp/dist/index.js"],
      "env": {
        "STEAM_API_KEY": "your_api_key_here",
        "STEAM_ID": "your_vanity_url_or_64bit_id"
      }
    }
  }
}

Configuration

Environment variable

Required

Description

STEAM_API_KEY

Yes

Your Steam Web API key

STEAM_ID

Yes

Your 64-bit Steam ID or vanity URL username

STEAM_MCP_CACHE_DIR

No

Override cache directory (default: ~/.steam-mcp/cache/)


Caching

Steam data is cached locally to keep responses fast and avoid hitting rate limits:

Data

Cache TTL

Library

1 hour

Recently played

30 minutes

Game details

24 hours

Use the refresh_library tool to clear the cache immediately (e.g., after buying new games).


Troubleshooting

"Steam returned no library data" Your Steam profile or game library is set to private. Go to Steam → your profile → Edit Profile → Privacy Settings and set both to Public.

"Could not resolve Steam vanity URL" Check that STEAM_ID matches the username in your Steam profile URL (steamcommunity.com/id/YOUR_USERNAME). Alternatively, use your numeric 64-bit Steam ID.

"Could not validate Steam API key" Verify your API key at steamcommunity.com/dev/apikey. Keys are tied to your Steam account login.

Tools not showing in Claude Restart Claude Desktop fully (quit from the system tray, not just close the window) after editing the config file. Check that Node.js 18+ is installed by running node --version in a terminal.


License

MIT

Available Tools

5 tools
get_game_detailsA

Get store details for a game — description, genres, tags, release date, Metacritic score, and price. Accepts game name or appid.

Inputs: name, appid.

get_libraryA

Get your full Steam game library with playtime and last-played date for each game.

Inputs: include_unplayed.

get_recently_playedB

Get games played in the last 2 weeks, with hours played this period and total.

Inputs: count.

refresh_libraryA

Clear the local cache so the next query fetches fresh data from Steam. Use after buying new games.

Inputs: no named parameters.

search_libraryC

Search and filter your Steam library by name, playtime range, or unplayed status.

Inputs: limit, query, max_hours, min_hours, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: store details, full library, recent games, cache refresh, and library search. No overlap between tools.

    Naming Consistency5/5

    All tools follow a verb_noun pattern using snake_case (get_, refresh_, search_). Verbs are descriptive and consistent across the set.

    Tool Count5/5

    5 tools is well-scoped for a Steam library server, covering browsing, searching, details, and cache management without unnecessary bloat.

    Completeness4/5

    Core library operations (view, search, details, cache) are covered. Minor gaps like achievements or wishlist management, but these are reasonable omissions for the scope.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers