Skip to main content
Glama
yuxiang115

opendota-mcp

by yuxiang115
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to opendota-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-riot-games

      pipeworx-io
      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.
      10 npm
      MIT

    • mcp-stratz

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Dota 2 data (hero stats, player matches, player heroes) via the STRATZ API, with support for arbitrary GraphQL queries.
      2 npm
      MIT

    • openfoot-mcp

      bartokulus
      A
      license
      A
      quality
      B
      maintenance
      Provides AI agents with real football data from the OpenFoot API, including fixtures, standings, lineups, live events, shot-level xG with pitch coordinates, league tables, and fair odds.
      12
      32 npm
      MIT

    • faceit-mcp

      justinbchau
      F
      license
      A
      quality
      B
      maintenance
      Enables Claude to query FACEIT CS2 stats including player profiles, lifetime stats, match history, and detailed per-match statistics via the FACEIT Data API.
      5
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 42 tools

    Disambiguation4/5

    Tools are clearly organized by primary entity (player, hero, team, league, match) and most have a singular purpose; similarly named tools like get_player_matches and get_player_recent_matches are distinguishable by their descriptions. A few player-stat tools (totals, counts, histogram, heroes) overlap in subject but differ in output shape, so some care is still needed.

    Naming Consistency5/5

    Nearly all tools follow a consistent get_<resource>_<detail> snake_case pattern, such as get_player_matches, get_team_heroes, and get_hero_matchups. Action verbs like request, refresh, search, and list are used only where appropriate, with no style mixing or vague naming.

    Tool Count2/5

    42 tools is a very large surface for an MCP server and exceeds the comfortable range, making agent selection harder even though the tools are well-named. Many related stat tools could be consolidated into fewer parameterized tools without losing functionality.

    Completeness4/5

    The set covers core read-only Dota 2 workflows well: player history and stats, hero matchups and benchmarks, teams, leagues, pro matches, match parsing, constants, and name resolution. A few niche OpenDota endpoints such as player ability/item usage are missing, but there are no obvious workflow dead-ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources