Provides tools for accessing Riot Games data including account lookup by Riot ID or PUUID, summoner details, match IDs, ranked league entries, and champion mastery information.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-riot-games Get match history for summoner 'Doublelift' on NA server."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Riot Games API MCP — League of Legends + TFT + Valorant + LoR public data. Free dev key (24h, 100 req / 2 min); apply for permanent key for production.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Platform: PLATFORM_RIOT_KEY. BYO: ?_apiKey=….
Related MCP server: MCP Riot Server
account_by_riot_id(region, game_name, tag_line) — riot ID → puuid (region = americas | europe | asia)
account_by_puuid(region, puuid) — account by puuid
summoner_by_puuid(platform, puuid) — summoner detail (platform = na1 | euw1 | …)
summoner_by_name(platform, name) — deprecated, use riot-id flow
match_ids_by_puuid(region, puuid, start?, count?, queue?, type?, startTime?, endTime?) — recent match ids
match(region, match_id) — match detail
match_timeline(region, match_id) — match timeline
league_entries(platform, queue, tier, division, page?) — ranked entries
champion_rotations(platform) — free champion rotation
champion_mastery(platform, puuid) — champion mastery
summoner_top_mastery(platform, puuid, count?) — top N mastery
status(platform) — platform status
https://<region|platform>.api.riotgames.com
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"riot-games": {
"url": "https://gateway.pipeworx.io/riot-games/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/riot-games/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Riot Games data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Provide detailed Pokémon data and information through a standardized MCP interface. Enable LLMs an…
Give your agent live data from Twitter, Reddit, the web and GitHub. No API keys, no scraping stack.
Discover, inspect and run 63,000+ agent tools from one balance. Pay per call, no subscriptions.
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
