MCP Server

MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. League of Legends AI coaching: player profiles, match history, ranked stats & performance analysis.

What you get

League of Legends MCP Server connects AI assistants to LoL data via the Riot Games API. 25 tools for player profiles, ranked stats, match history, champion mastery, live game detection, league standings, Clash tournaments, challenges - plus AI-powered performance analysis and coaching.

• AI Coaching — Claude analyzes your matches and generates detailed coaching reports
• Data Dragon Integration — Champion, item, rune, and spell names automatically resolved
• Intelligent Caching — Smart TTL-based caching to reduce API calls
• 16 Regions — EUW, NA, KR, BR, LA, OC, TR, RU, JP, PH, SG, TH, TW, VN, and more

Configuration and credentials

You will need one environment variable: YOUR_APIFY_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by ebrunet001; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.