Skip to main content
Glama
Sign In
SDNick484

mcp-server-steam-backlog

by SDNick484
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-server-steam-backlog

No user-submitted related servers found.

    Related Servers

    • steam-personal-mcp

      megabaka404
      F
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that enables AI assistants to access a user's Steam library, playtime, achievements, friends, wishlist, and store data for backlog analysis, game recommendations, discount monitoring, and play-activity summaries.
      -

    • Game Hub

      ccjacobs94
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and manage a unified multi-platform game library, including playtime, achievements, ratings, backlog status, recommendations, duplicate reconciliation, and genre enrichment through MCP tools.
      MIT

    • steam-mcp

      inerthel-agi
      A
      license
      A
      quality
      B
      maintenance
      Exposes Steam Web API tools as MCP resources for Claude Code, Claude Desktop, and Gemini CLI, enabling profile lookups, game searches, achievement tracking, and more.
      11
      25 npm
      1
      MIT

    • steam-mcp

      jkiley129
      A
      license
      A
      quality
      D
      maintenance
      Connects Claude to your Steam library via the Steam Web API. Query your games, playtime, recently played history, and store metadata using natural language. Zero-config install via npx steam-mcp.
      5
      25 npm
      6
      MIT

    • steam-mcp

      brandikun
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that connects AI assistants to the Steam Web API and storefront, enabling game library analysis, mood-based backlog recommendations, wishlist evaluation, and storefront searches.
      8
      18 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: search (find_games), single-game detail (get_game), summary (get_overview), recommendation (suggest_picks), queue read vs. reorder, note write, lane write, and export start vs. status. The descriptions explicitly cross-reference each other (e.g. find_games says to use suggest_picks for recommendations), eliminating the main potential overlap.

    Naming Consistency5/5

    All ten tools share the backlog_ prefix and follow a consistent snake_case verb_noun pattern (find_games, get_game, set_lane, reorder_next, start_export). No mixed conventions or vague verbs.

    Tool Count5/5

    Ten tools is well within the ideal 3-15 range and each maps to a clear, non-redundant capability for a backlog dashboard: read, filter, recommend, triage, annotate, order, and refresh. Nothing feels padded or missing a counterpart.

    Completeness4/5

    The lifecycle is well covered: overview, filtered search, per-game detail, ranked picks, lane transitions, note management (including clearing), queue ordering, and export start/status. Minor gaps exist (no dedicated lane-listing beyond filter-by-lane in find_games, no batch note operations), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources