steam-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STEAM_ID | Yes | Your 64-bit Steam ID or vanity URL username | |
| STEAM_API_KEY | Yes | Your Steam Web API key | |
| STEAM_MCP_CACHE_DIR | No | Override cache directory (default: ~/.steam-mcp/cache/) | ~/.steam-mcp/cache/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_libraryA | Get your full Steam game library with playtime and last-played date for each game. |
| get_recently_playedB | Get games played in the last 2 weeks, with hours played this period and total. |
| search_libraryC | Search and filter your Steam library by name, playtime range, or unplayed status. |
| get_game_detailsA | Get store details for a game — description, genres, tags, release date, Metacritic score, and price. Accepts game name or appid. |
| refresh_libraryA | Clear the local cache so the next query fetches fresh data from Steam. Use after buying new games. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: store details, full library, recent games, cache refresh, and library search. No overlap between tools.
All tools follow a verb_noun pattern using snake_case (get_, refresh_, search_). Verbs are descriptive and consistent across the set.
5 tools is well-scoped for a Steam library server, covering browsing, searching, details, and cache management without unnecessary bloat.
Core library operations (view, search, details, cache) are covered. Minor gaps like achievements or wishlist management, but these are reasonable omissions for the scope.