Skip to main content
Glama
hkaanengin

opendota-mcp-server

by hkaanengin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to opendota-mcp-server

No user-submitted related servers found.

    Related Servers

    • opendota-mcp

      yuxiang115
      A
      license
      B
      quality
      B
      maintenance
      Enables LLMs and agents to query Dota 2 matches, players, heroes, teams, and pro scene data through the OpenDota API, with numeric IDs resolved to localized names and readable labels.
      42
      72 npm
      MIT

    • mcp-stratz

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

    • OpenDota MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query Dota 2 hero meta statistics, recent professional matches, search players by display name, and retrieve player profiles by account ID. It exposes these capabilities as MCP tools over gateway or local stdio connections.
      17 npm
      MIT

    • mlbb-mcp

      cebarrett
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Mobile Legends: Bang Bang hero data including win rates, counters, synergies, and builds via natural language.
      -

    • rgl-mcp

      RGLgg
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying RGL.gg competitive TF2 data through natural language, resolving player, team, season, division, and match information via a series of API calls.
      -
    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

    A4.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource: player profile, win/loss, heroes, totals, histograms, peers, match details, heroes, items, aghs upgrades, matchups, item popularity, benchmarks, records, and scenario timings. The descriptions explicitly cross-reference similar tools to prevent confusion, e.g., 'For simple win/loss counts, use get_player_win_loss() instead'.

    Naming Consistency4/5

    All tools use a 'get_' prefix except for request_parse_match, which breaks the pattern. While most names are clear and consistent (get_player_*, get_hero_*, get_scenarios_*), minor grammatical variations like get_heroes_played (past participle) and get_player_win_loss (compound noun) create slight inconsistency.

    Tool Count4/5

    18 tools is slightly above the typical well-scoped range of 3-15, but justified given the broad Dota 2 domain covering players, matches, heroes, items, records, and scenarios. The count is manageable and each tool has a unique purpose, though it borders on heavy.

    Completeness4/5

    The toolset covers the core lifecycle: player overview, detailed match info (including parse request), hero reference, item reference, and various analytics. Minor gaps exist (no list-all-heroes/items tool, no opponent-only stats, no global hero tier list), but agents can work around these using the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources