The scope is deliberately narrow: history and detail for the player whose Riot ID is baked into the launch command. That makes it a straightforward way to have a model reason over your own games, and it means the 24-hour development key is the first thing that will trip you up if the answers suddenly stop coming.
A small stdio server that reads Team Fight Tactics data for one player through the Riot Games API. Your Riot ID is fixed at launch, so every question is about your own account rather than an arbitrary summoner.
- `tft_match_history` returns your recent matches; `count` defaults to 20 and `start` defaults to 0 for paging further back
- `tft_match_details` returns the full detail for one match, given its `matchId`
- Everything runs over stdio, so the client starts and stops it for you
The npm package `mcp-server-tft`, version 0.1.3, launched with `npx` on Node.js v14 or higher. It takes three command-line arguments: a Riot Games API key, your Game Name and your Tag Line (the part after the name, such as NA1). Development keys from the Riot developer portal expire after 24 hours; a permanent personal key needs an application.
One command plus a key — npx -y mcp-server-tft, then supply credentials