This MCP server provides access to Team Fight Tactics data through two main tools: tft_match_history and tft_match_details. The tft_match_history tool returns the TFT match history for the current player, with optional pagination parameters such as count (default 20) and start (default 0). The tft_match_details tool fetches detailed information about a specific TFT match by providing the matchId. To use the server, configure the MCP client (for example, via Claude Desktop) with the provided npx command that includes your Riot API key, game name, and tag line. Once running, send requests to the available tools to retrieve your match history or specific match details.

Prerequisites:

• Node.js (v14 or higher)
• npm or yarn
• Riot Games API Key (for TFT data)
• Your TFT game name and tag line (from Riot/competition UI)

Installation steps:

1. Ensure Node.js and npm are installed. Verify with: node -v npm -v
2. Install or clone the MCP server package (example using npm): npm install -g mcp-server-tft

   or if you are developing locally, clone the repo and run npm install in the project directory

3. (Optional) Build the project if using a local source repo: npm run build
4. Start the server via npx as described in the usage config, or run the local script if you are developing: npx mcp-server-tft --apiKey <YOUR_RIOT_API_KEY> --gameName <YOUR_GAME_NAME> --tagLine <YOUR_TAG_LINE>
5. Verify the server is running and respond to MCP protocol requests from your client configuration.

Notes and tips:

• The Riot API key can be a temporary key for development (expires in ~24 hours). For production, apply for a permanent API key.
• The server runs via stdio as an MCP endpoint. Ensure your client is configured to communicate using the MCP protocol.
• If you encounter rate limits or authentication errors, check that the API key is correctly provided and that you’re using the proper gameName and tagLine as configured in Riot's portal.
• This server is written in TypeScript and uses the Model Context Protocol SDK; to modify, edit the src directory and rebuild with npm run build, then test with npm start.
• If you plan to deploy, consider environment-based configuration for API keys and game identifiers rather than embedding them directly in commands.