mcpField
R
Riot Games

Riot Games

Remote
pipeworx.ioGames & Entertainment0Updated 3w ago

About Riot Games

Riot Games is an MCP server for accessing public Riot Games API data for League of Legends, TFT, Valorant, and LoR. It includes account, match, ranking, mastery, rotation, and platform-status tools; an API key is required.

Key features

  1. 01Look up accounts and summoners
  2. 02Retrieve match details and timelines
  3. 03Query match IDs and ranked entries
  4. 04Check champion rotations and mastery
  5. 05View platform status

Use cases

  1. 01Inspect a player's recent matches
  2. 02Review match details and timelines
  3. 03Look up ranked entries or champion mastery

MCP support

Exposes Riot Games API tools through a Pipeworx gateway endpoint or a local stdio MCP server. The API requires a Riot key; the gateway also supplies shared Pipeworx meta-tools, while the local server exposes only this pack’s tools.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/riot-games/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

@pipeworx/riot-games

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 1743+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Auth

  • Platform: PLATFORM_RIOT_KEY. BYO: ?_apiKey=….

Tools (LoL)

  • 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

Data source

https://<region|platform>.api.riotgames.com

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "riot-games": {
      "url": "https://gateway.pipeworx.io/riot-games/mcp"
    }
  }
}
What this endpoint actually serves

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 1743+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/account_by_riot_id. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "riot-games": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-riot-games"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-riot-games

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

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.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.