Access TFT Match Data
MCP server exposing TFT match history and match-detail lookups via the Riot Games API.
Why it matters
Connect to the Team Fight Tactics game data via the Model Context Protocol. Retrieve comprehensive match history and detailed match information for players.
Outcomes
What it gets done
Retrieve TFT match history for a summoner.
Get detailed information about specific TFT matches.
Integrate with Riot Games API for real-time data access.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-tft-match-analyzer | bash Capabilities
Tools your agent gets
Get TFT match history for the current player with optional count and start parameters for pagination
Get detailed information about a specific TFT match using the match ID
Overview
TFT-Match-Analyzer MCP Server
This MCP server exposes TFT match history and per-match detail lookups via the Riot Games API, configured with a Riot API key and Riot ID (Game Name + Tag Line). Use it when an AI agent needs to pull TFT match history or inspect a specific match's details - it does not cover live-game or spectator data.
What it does
Provides an MCP server for Team Fight Tactics (TFT) that exposes TFT match data through two tools: retrieving a summoner's match history, and retrieving detailed information about a specific TFT match.
{
"mcpServers": {
"tft-mcp": {
"command": "npx",
"args": [
"mcp-server-tft",
"--apiKey",
"<YOUR_RIOT_API_KEY>",
"--gameName",
"<YOUR_GAME_NAME>",
"--tagLine",
"<YOUR_TAG_LINE>"
]
}
}
}
The tft_match_history tool returns TFT match history for the current player, with optional count (number of matches to retrieve, defaults to 20) and start (pagination start index, defaults to 0) parameters. The tft_match_details tool returns detailed information about one match, given a required matchId parameter. The server runs on stdio and is built in TypeScript on the Model Context Protocol SDK.
When to use - and when NOT to
Use it when an AI agent needs to pull a player's TFT match history or inspect the details of a specific TFT match via the Riot Games API. It only covers these two read operations - it is not a general Riot Games API client or a live-game/spectator tool.
Inputs and outputs
Configuration requires a Riot Games API key (a temporary key expires in 24 hours during development; production use needs a permanent personal key from Riot's Application Portal), plus the player's Riot Game Name and Tag Line (e.g. NA1, shown after the Game Name in the Riot client). Tool inputs are match-history pagination parameters or a match ID; outputs are match history lists or per-match detail objects.
Capabilities
Two tools: tft_match_history (paginated match history retrieval) and tft_match_details (full detail for a single match by ID). Both require a valid Riot Games API key and Riot ID (Game Name + Tag Line) supplied at server startup.
How to install
Requires Node.js v14+ and npm or yarn. Configure it in the Claude Desktop config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%/Claude/claude_desktop_config.json on Windows) with the npx mcp-server-tft command and the API key, game name, and tag line as arguments, as shown above. For development, modify code in the src directory, run npm run build to compile, and npm start with the required parameters to test changes. The project is MIT licensed.
Who it's for
Players and developers who want an AI agent to pull their TFT match history or inspect specific TFT match details directly from the Riot Games API, without building a Riot API client themselves.
Source README
TFT MCP Server
This is a Model Context Protocol (MCP) server for Team Fight Tactics (TFT) that provides access to TFT game data through various tools.
Features
- Get match history for a summoner
- Get detailed information about specific TFT matches
Prerequisites
- Node.js (v14 or higher)
- npm or yarn
- Riot Games API Key (for accessing TFT data) - Get it from Riot Games Developer Portal
- Note: For development, you can use a temporary API key that expires in 24 hours
- For production use, you'll need to apply for a permanent personal API key at Riot's Application Portal
- Your Game Name, accessed from your Riot game console
- Your Name Tagline, accessed from your Riot game console, which is usually followed/shown right after your Game Name. For example:
NA1
Usage
- Configure the MCP server in your Claude Desktop config file:
MacOS
Location: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows
Location: %APPDATA%/Claude/claude_desktop_config.json
Add the following configuration:
{
"mcpServers": {
"tft-mcp": {
"command": "npx",
"args": [
"mcp-server-tft",
"--apiKey",
"<YOUR_RIOT_API_KEY>",
"--gameName",
"<YOUR_GAME_NAME>",
"--tagLine",
"<YOUR_TAG_LINE>"
]
}
}
}
- The server will run on stdio and provide the following tools:
tft_match_history
Get TFT match history for the current player.
Parameters:
count(optional): Number of matches to retrieve. Defaults to 20start(optional): Start index for pagination. Defaults to 0
tft_match_details
Get detailed information about a specific TFT match.
Parameters:
matchId(required): The match ID to get details for
Development
The project is written in TypeScript and uses the Model Context Protocol SDK. To modify the code:
- Make changes in the
srcdirectory - Run
npm run buildto compile - Run
npm startwith the required parameters to test changes
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.