RiotSkillIssue
Typed async and sync Riot Games APIs, plus an optional local MCP server.
Install
RiotSkillIssue 1.0 requires Python >=3.14,<3.17, covering Python 3.14,
3.15, and 3.16. As of July 2026, CI gates releases on Python 3.14 and the
current Python 3.15 prerelease. Python 3.16 is still in development, so it is
covered by a non-blocking nightly compatibility probe until its stable release.
pip install riotskillissue
Set RIOT_API_KEY or pass a key directly:
import asyncio
from riotskillissue import PlatformRoute, RiotClient
async def main() -> None:
async with RiotClient(
api_key="RGAPI-...",
default_route=PlatformRoute.EUW1,
) as riot:
profile = await riot.lol.player_profile("Player#EUW")
history = await riot.lol.match_history("Player#EUW", count=5)
match = await riot.raw.lol.match.get_match(match_id="EUW1_...")
print(profile, history, match)
asyncio.run(main())
The explicit synchronous client provides the same workflows and raw operation groups:
from riotskillissue import PlatformRoute, SyncRiotClient
with SyncRiotClient(default_route=PlatformRoute.EUW1) as riot:
print(riot.lol.player_profile("Player#EUW"))
Local MCP server
Install the optional server and run it over stdio:
pip install "riotskillissue[mcp]"
riotskillissue-mcp
The server reads credentials from its environment. API keys and RSO tokens are
never tool arguments. Raw write operations are hidden unless
RIOT_MCP_ALLOW_WRITES=true; enabled writes still require human confirmation.
Coverage and generation
The generated raw API covers every operation in the bundled community-maintained OpenAPI feed. That feed is not an official Riot Games specification. One committed operation registry drives raw dispatch, reference documentation, and MCP discovery.
RiotSkillIssue is not endorsed by Riot Games and does not reflect the views or opinions of Riot Games or anyone officially involved in producing or managing Riot Games properties. Riot Games and all associated properties are trademarks or registered trademarks of Riot Games, Inc.
License
MIT. See LICENSE.
Metadata
Release files for riotskillissue 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| riotskillissue-1.0.0.tar.gz | 935.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| riotskillissue-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / riotskillissue-1.0.0.tar.gz
| Download URL | riotskillissue-1.0.0.tar.gz |
|---|---|
| Size | 935.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d20eed3035f6747aaff502afa5de64068e141e5aea248cbddddb80eedef6140
|
|
BLAKE2b-256 checksum How to use checksums |
5a969c04188ff30498e19725f6326eb00a9338b986d50a9d315827ce57b91936
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 31, 2026.
Transparency logRelease files / riotskillissue-1.0.0-py3-none-any.whl
| Download URL | riotskillissue-1.0.0-py3-none-any.whl |
|---|---|
| Size | 168.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6175513a865d10ea4075b7096ef622d2b1dfe14758b3df5ff0a3000da24d9d1
|
|
BLAKE2b-256 checksum How to use checksums |
bab047349e5a881fab8ec2caa8e81daa435a28d79fffaa993a3267d1b897c864
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 31, 2026.
Transparency log