Skip to main content
Glama
649,985 tools. Updated 2026-10-11 07:04

"Riot Games" matching MCP tools:

  • A player's recent games with every raw box-score stat per game — one call instead of one request per event. Use this to answer 'how has X actually performed lately?' and to build L5/L10/L20, season splits and head-to-head yourself. Pass `opponent` for H2H (accepts a full name, nickname or abbreviation — 'Boston Red Sox', 'Red Sox', 'BOS'); the limit applies AFTER that filter, so opponent + limit=10 means the last 10 MEETINGS, not the Boston games among the last 10 games. H2H is not capped to the current season. IMPORTANT: this is the raw box-score archive, NOT graded-prop history — it covers every game with a box score on file, including games no sportsbook priced, so a 'last 10 games' window here really is the last 10 games (one built from propline_get_player_trends silently skips unpriced games). It carries no line, price or grade; use propline_get_player_trends for hit rates against a posted line. `player_team`/`opponent`/`is_home` are null when the player's side can't be identified, and always for individual sports (tennis, golf, UFC) — report them as unknown rather than guessing. Accepts a player_id in place of the name; the response carries player_id (null when the player has none yet).
    ConnectorNo auth
  • Admin-only: community findings grouped per author IP — count, first/last submission, games, categories, tags and the latest title — ordered by volume. Use to spot a contributor flooding the corpus, to find the IP behind a batch of bad findings, or as the entry point before `admin_list_findings({ authorIp })` / `admin_search_findings({ authorIp })` to pull that author's rows. `sinceDays` counts only recent submissions; `authorIp` returns that one author. Findings submitted before IP capture existed show as `authorIp: null`. Spans both games (the DB is shared) — each row says which.
    ConnectorOAuth
  • Admin-only: community findings grouped per author IP — count, first/last submission, games, categories, tags and the latest title — ordered by volume. Use to spot a contributor flooding the corpus, to find the IP behind a batch of bad findings, or as the entry point before `admin_list_findings({ authorIp })` / `admin_search_findings({ authorIp })` to pull that author's rows. `sinceDays` counts only recent submissions; `authorIp` returns that one author. Findings submitted before IP capture existed show as `authorIp: null`. Spans both games (the DB is shared) — each row says which.
    ConnectorOAuth
  • Steam games for someone who likes 1-3 given games, ranked by imho.run's recommender: the list imho.run's own tool shows for those games and filters. Use it instead of games_like when the user names several games, wants filters beyond free / co-op / Steam Deck (no PvP, no microtransactions, no grind, not too hard, no Early Access, release years, more niche or more popular), or says what they want in words: pass that as `preferences` ('cozy base building, no combat'); the result says which Steam tags it was read as. When the user reacts to the picks, call it again with `liked` / `disliked`: liked games join the seeds, disliked ones never come back. Each pick has a one-line reason naming the seed it is closest to (`similar_to`), price, Steam Deck status, year, reviews, the imho.run URL and the Steam URL, plus `tool_url` (these games in imho.run's tool). Not for naming a game from a description (find_game_by_description) or facts about one game (game_facts). Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.
    ConnectorNo auth
  • Games released on Steam in the last 30 days that players rate well (70%+ positive, 50+ positive reviews), or with `upcoming` the upcoming games that have a release date; optionally co-op only. The site's New releases list, with price, Steam Deck status, release date and links. Released games carry `release_kind`: `new`, or `ea_exit` for a game that just left Early Access (its 1.0; it was playable before), so call those 'out of Early Access', not new. `ea_exits`: include (default), exclude (brand-new games only) or only. Use it for 'what's new / coming out'; for what is gaining players now use trending. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.
    ConnectorNo auth
  • Games scheduled/played on one calendar date (US-Eastern) for nba, mlb, or nhl; defaults to today. Returns the same envelope as query_table on the games table. NFL is week-based, not date-based — for nfl, use query_table on nfl/games with season_id + week filters instead. Requires an API key; rows count against quota.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to query Riot Games data such as accounts, summoners, match history, and champion mastery via natural language.
    187 npm
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    A community-developed Model Context Protocol server that integrates with the Riot Games API to provide League of Legends data, enabling AI assistants to retrieve player information, ranked stats, champion mastery, and match summaries through natural language queries.
    5
    27
    MIT

Matching MCP Connectors

  • Riot Games API MCP.

  • Build, publish and update browser games with saves, leaderboards and realtime multiplayer built in.

  • Return today's games that have player props available for a sport. Read-only. No side effects. Requires an API key; rate-limited per your tier. Returns: { sport, count, games: Array<{ id, sport, homeTeam, awayTeam, startTime, live, source }> }. id is the eventId to pass to get_game_props (prefixed ud- for Underdog or sc- for the soccer odds board); live is true when the game is in progress; source is "underdog" or "theoddsapi". Live games sort first; scheduled games follow. Typical workflow: call list_games to discover eventIds, then pass an eventId to get_game_props. If sport is omitted the server selects the active in-season league automatically. Returns count=0 with an empty games array (not an error) when no props are posted yet for the day. When to use: to browse all games on the slate or to find an eventId before calling get_game_props. When not to use: if you already have the eventId, skip this and call get_game_props directly. Use find_game instead when you know the team names but want a single-game eventId without browsing the full slate.
    ConnectorNo auth
  • Tennis season return-games-won leaderboard: Share of return games won per player (breaks over opponent service games played), from real match-stats aggregates read return-side, ordered highest pct first. When to use: - Share of return games won per player (breaks over opponent service games played), from real match-stats aggregates read return-side, ordered highest pct first. season tables; clutch/serve-efficiency leader queries. Prefer over: raw leaderboard via call_api for agent-normalized rows. Do not use when: ranking position → standings with game tennis; week-over-week movement → rankings_movers; one player's recent form → player_form. Tennis-only. Season defaults to 2026; tour (ATP|WTA) is optional — omit it for the combined board. Only players with at least 100 return games played qualify. Parallel-safe: yes. Upstream cost: 1.
    ConnectorNo auth
  • Steam games for a player, ranked against their own public Steam library (what they play most), the way imho.run's library mode does it; owned games are left out. Use it when the user gives their Steam profile and wants picks for their taste in general; for 'games like X' use games_like or recommend. Takes a SteamID64 or a steamcommunity.com/profiles/<SteamID64> link (not a custom /id/ name) and works only for public profiles imho.run already has; otherwise it returns one 'unavailable' error with a link the user can open to paste their profile. Each pick names the most-played game it is closest to (`similar_to`). Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.
    ConnectorNo auth
  • Get detailed information about board games on BoardGameGeek (BGG) including description, mechanics, categories, player count, playtime, complexity, and ratings. Use this tool to deep dive into games found via other tools (e.g. after getting collection results or search results that only return basic info). Use 'name' for a single game lookup by name, 'id' for a single game lookup by BGG ID, or 'ids' to fetch multiple games at once (up to 20). Only provide one of these parameters.
    ConnectorOAuth
  • Where to buy a video game. Not live yet: every call returns an explicit "coming soon" — no links, no prices — and contacts no store. Tell the user plainly that games aren't supported yet; never guess a store link or a price. For music, use resolve_music. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.
    ConnectorNo auth
  • Start here when the category is unclear. Pass the user's words as `query`; RootVine reads music or games from them (keyword-based — set `category` when you know it) and answers in that tool's shape. Music is live; games answer "coming soon" for now. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.
    ConnectorNo auth
  • Full text of a Wikipedia article by title — the ACTUAL prose AND its tables, not just the lead paragraph. This is how you read a competition schedule, fixture list, medal table, results grid or roster: get_article_extract({title: "Table tennis at the 2026 Asian Games"}) returns the venue, the dates and the day-by-day event schedule. Answers "when is <sport> at <the games>", "what are the <event> dates", "who won <medal event>", "explain X in detail", "what does the article say about <topic>", reading the history/methods/etc. CALL IT DIRECTLY when the title is predictable from the question — Wikipedia titles are regular, so "when is table tennis at the Asian Games" is the article "Table tennis at the 2026 Asian Games", and the same pattern gives "Athletics at the 2028 Summer Olympics", "India at the 2026 Asian Games", "2026 FIFA World Cup". Constructing the title and reading the article beats searching first, because the search snippet is one truncated line and this returns the whole thing. Titles are exact: on a miss you get a user_error naming search_wikipedia as the recovery. PREFER OVER get_article_summary whenever the lead paragraph is not enough. Omit section for the whole article (capped by max_chars); pass a section number (from get_article_sections) for just that one. Returns plain text with headings marked == like this == and table rows one per line, cells separated by | .
    ConnectorNo auth
  • The current storefront/platform revenue cuts RoyalTea models — Steam, Epic Games Store (+ First Run), Apple, Google Play, console, itch.io — with exact tiers, thresholds, and the Unreal Engine royalty. Use to explain or cite what a given platform takes.
    ConnectorNo auth
  • Get structured metadata for a game: players, duration, complexity, mechanics, how_to_play, variant list, page list, related games. Lightweight alternative to fetching the full rulebook.
    ConnectorNo auth
  • Use when querying past or future games with filters. Returns scores, teams, venue, and game metadata. For upcoming-only games, prefer get_schedule (2 cr) instead. Costs 5 credits.
    ConnectorNo auth
  • Use when checking what games are coming up. Returns only unplayed future games for the next N days (default 7). For past games, use get_games instead. Costs 2 credits.
    ConnectorNo auth
  • Use when querying past or future games with filters. Returns scores, teams, venue, and game metadata. For upcoming-only games, prefer get_schedule (2 cr) instead. Costs 5 credits.
    ConnectorNo auth
  • Use when checking what games are coming up. Returns only unplayed future games for the next N days (default 7). For past games, use get_games instead. Costs 2 credits.
    ConnectorNo auth
  • Use when querying past or future games with filters: season, week, team, date range, game type, status. Returns scores, kickoff (UTC), venue, rest days, starting QBs, coaches, referee, and the consensus closing spread, total, and moneylines. For upcoming-only games prefer get_schedule (2 cr). Costs 5 credits.
    ConnectorNo auth