MCP Steam Server

Created By
dspa year ago
MCP Server for interacting with Steam
Overview

what is MCP Steam Server?

MCP Steam Server is a Model Context Protocol (MCP) server that provides Steam gaming context to AI assistants, integrating with the Steam API to fetch user gaming information and preferences.

how to use MCP Steam Server?

To use the MCP Steam Server, you can run it using Docker with the command: docker run --rm -i ghcr.io/dsp/mcp-server-steam:latest. Configure it by setting the required environment variable STEAM_API_KEY with your Steam API key.

key features of MCP Steam Server?

  • Integrates with the Steam API to access user gaming data.
  • Exposes gaming context through the Model Context Protocol (MCP).
  • Allows AI assistants to understand user gaming activities and preferences.

use cases of MCP Steam Server?

  1. Enabling AI assistants to provide personalized gaming recommendations.
  2. Fetching user gaming statistics for analysis.
  3. Enhancing user interaction with AI through gaming context.

FAQ from MCP Steam Server?

  • What is required to run the MCP Steam Server?

You need Docker and a valid Steam API key to run the server.

  • Can I contribute to the MCP Steam Server?

Yes! Contributions are welcome, and you can submit a Pull Request on GitHub.

  • Is there documentation available for the API?

Yes, detailed API documentation can be found at the MCP Documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dsp
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago