liquipedia-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIQUIPEDIA_API_KEY | Yes | Your LPDB API key. Sent only in the Authorization header; never logged. | |
| LIQUIPEDIA_USER_AGENT | Yes | Identifies your project and how to reach you, e.g. "<your-project>/<version> (<contact>)" → "esports-helper/1.2 (https://github.com/you/esports-helper; you@example.org)". | |
| LIQUIPEDIA_LOCKOUT_SECONDS | No | Pause after an HTTP 429 (default 600, minimum 60). | 600 |
| LIQUIPEDIA_MAX_REQUESTS_PER_HOUR | No | Lower the per-process budget (1–60, default 60). Values above 60 are refused. | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_resultsA | Finished matches, newest first, with the series score, the winner by name and the score of every single game (e.g. 3–2 OT), so you can tell close series from one-sided ones. Filter by team and/or exact tournament name; without either, only top-tier matches (max_tier, no qualifiers/showmatches unless include_minor_types) are returned. With 3 matches or fewer, League of Legends champion picks and MVPs are included. Read each line on its own and do not invent totals. Cite Liquipedia as the source. |
| get_upcomingA | Scheduled matches from now on, soonest first (times in UTC; 'time TBA' when only the day is known). Filter by team and/or exact tournament; without either, only top-tier matches (max_tier, no qualifiers/showmatches unless include_minor_types). These matches have no result yet: never present them with a score. Pairings with undetermined (TBD) opponents are left out. Cite Liquipedia as the source. |
| get_matches_betweenA | All matches between two UTC timestamps (max. 31 days), in chronological order, for one or more wikis in a single request – e.g. 'what's on this weekend' or 'what happened yesterday'. Finished matches show score and winner; the others are marked 'not played yet' and have no score. Without a team only top-tier matches (max_tier, no qualifiers/showmatches unless include_minor_types) are returned. Matches whose time is not announced count as whole days: they are included only if their UTC day lies fully inside the range (or the range inside that day), and many of them are summarised per tournament stage. Up to 50 matches with a known time are listed; the text says when the list was cut off. Cite Liquipedia as the source. |
| get_standingsA | League, group or Swiss standings. Preferred: pass the team – this finds the phase the team is currently playing in (works when you only know 'Worlds' or 'LCK') and names its next phase if one is scheduled. Alternatively pass the exact tournament name to get all groups of its newest stage. Each row: placement, team, match record, game record (when meaningful), advanced/eliminated if decided. If a table is 'Not started yet', there is no leader. Cite Liquipedia as the source. |
| get_match_detailsA | Every game of a team's most recent finished match(es): game scores, overtime, game length, kills and maps where available, MVPs and League of Legends champion picks per player. Optionally only matches against a given opponent. Use this for follow-up questions like 'was it close?' or 'who played which champion?'. Cite Liquipedia as the source. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Most tools target distinct query patterns: get_results for finished matches by team/tournament, get_upcoming for future matches, get_standings for tables, get_matches_between for date ranges, and get_match_details for deep per-game stats. However, get_results and get_matches_between both return finished match scores, and get_results sometimes includes champion picks/MVPs that get_match_details specializes in, creating mild overlap.
All tools use a consistent get_ prefix with snake_case noun phrases (get_results, get_standings, get_upcoming, get_matches_between, get_match_details). The pattern is predictable with no mixed conventions.
Five tools is well-scoped for a match-data server, covering results, standings, upcoming fixtures, date-range queries, and detailed game stats without redundancy or bloat.
The set covers core match lifecycle needs: finished results, upcoming fixtures, standings, time-range queries, and detailed game breakdowns. Minor gaps remain, such as direct tournament/team/player lookup or roster information, but agents can work around most common esports queries.