Skip to main content
pysteam-client

CI status CodeQL SAST OpenSSF Scorecard PyPI version Python versions MCP tools included License

pysteam-client

Modern Python client for the Steam network — CM protocol, PICS, CDN, WebAuth, Web API, Steam Guard, SteamIDs — plus a fully-async facade for FastAPI / TaskIQ and an MCP tool set for LLM agents.

Maintained fork of ValvePython/steam for Python 3.13+ and current Steam wire protocols. Full docs in the Wiki.

Install

pip install pysteam-client[client]

[client] pulls in the gevent-based SteamClient (login, PICS, CDN). Without it the requests-only subset (WebAPI / WebAuth / SteamID / master-server query) still works.

Quick start

Sync (script, CLI, batch jobs):

from steam.client import SteamClient

client = SteamClient()
client.anonymous_login()
info = client.get_product_info(apps=[440], timeout=15)
print(info["apps"][440]["common"]["name"])
client.logout()

Async (FastAPI, TaskIQ, any asyncio app):

from steam.aio import AsyncSteamClient

async with AsyncSteamClient() as client:
    await client.anonymous_login()
    info = await client.get_product_info(apps=[440])

MCP (expose to an LLM agent):

from mcp.server.fastmcp import FastMCP
from steam.aio import AsyncSteamClient
from steam.mcp import register_steam_tools

server = FastMCP("Steam")
client = AsyncSteamClient()
await client.start()
await client.anonymous_login()
register_steam_tools(server, client)   # steam.status, steam.get_product_info, steam.send_um

Documentation

Full documentation lives in the Wiki. Highlights:

Getting started

Client APIs

Async / FastAPI / MCP (new in 1.6)

Advanced

Security

Every push, PR, and release runs the following gates before any wheel ships to PyPI: ruff + black (style), mypy --strict (types), pytest (unit + integration), deptry (deps hygiene), bandit (Python SAST), pip-audit (CVEs), CodeQL (cross-file SAST), OpenSSF Scorecard (repo posture). A failing gate blocks the publish step.

Report a vulnerability: use GitHub Security Advisories (private, coordinated disclosure). Full policy in SECURITY.md. Do NOT open a public GitHub issue for security reports.

License

MIT — see LICENSE. Unchanged from upstream.

Metadata

Release files for pysteam-client 1.8.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pysteam-client 1.8.2
File Size Uploaded Provenance Actions
pysteam_client-1.8.2.tar.gz 948.8 kB With provenance Details for pysteam_client-1.8.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pysteam-client 1.8.2
File Interpreter ABI Platform Actions
pysteam_client-1.8.2-py3-none-any.whl Python 3 none any Details for pysteam_client-1.8.2-py3-none-any.whl

Total release size: 2.1 MB

Release files / pysteam_client-1.8.2.tar.gz

Download URL pysteam_client-1.8.2.tar.gz
Size 948.8 kB
Tags Source
SHA-256 checksum
How to use checksums
580f8db4e174169265eb29e2fe49ee56a1a37c87eb0110285c3ec74e4d15c3a5
BLAKE2b-256 checksum
How to use checksums
5071414af4da026764f9e19743b7ff5a6be1ef6dbd84555a5d0f64b7b1dc7fa7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.

Transparency log

Release files / pysteam_client-1.8.2-py3-none-any.whl

Download URL pysteam_client-1.8.2-py3-none-any.whl
Size 1.1 MB
Tags Python 3
SHA-256 checksum
How to use checksums
035d0f3e2bf4b34fa78931c378edcca861aeefe348ab5e51551be4949eeb6f42
BLAKE2b-256 checksum
How to use checksums
4d5605f3576e7125d4a9c0187ce30ef5b7bd309a2028b1b5e79433f75fa8e597
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.

Transparency log

Security for pysteam-client 1.8.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for pysteam_client-1.8.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page