2,500+ MCP servers ready to use
Vinkius

OpenDota MCP Server for LlamaIndex 18 tools — connect in under 2 minutes

Built by Vinkius GDPR 18 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add OpenDota as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to OpenDota. "
            "You have 18 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in OpenDota?"
    )
    print(response)

asyncio.run(main())
OpenDota
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About OpenDota MCP Server

Connect to OpenDota and explore the world's most comprehensive Dota 2 match database through natural conversation.

LlamaIndex agents combine OpenDota tool responses with indexed documents for comprehensive, grounded answers. Connect 18 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

What you can do

  • Player Profiles — Get player stats, rank tier, MMR estimate, winrate and most played heroes
  • Match History — Browse a player's full match history with hero, result, KDA and duration
  • Match Details — Get complete match info including all 10 players, items, builds, damage and objectives
  • Heroes — List all 124 Dota 2 heroes with their roles, attributes and performance benchmarks
  • Teams — Discover professional teams with their ratings, rosters and win/loss records
  • Leagues — Browse all pro leagues and tournaments with tiers and dates
  • Records — See all-time records for kills, GPM, XPM, hero damage and more
  • MMR Distribution — View rank tier distribution across the entire Dota 2 player base
  • Search — Find players, teams and leagues by name

The OpenDota MCP Server exposes 18 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect OpenDota to LlamaIndex via MCP

Follow these steps to integrate the OpenDota MCP Server with LlamaIndex.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 18 tools from OpenDota

Why Use LlamaIndex with the OpenDota MCP Server

LlamaIndex provides unique advantages when paired with OpenDota through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine OpenDota tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain OpenDota tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query OpenDota, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what OpenDota tools were called, what data was returned, and how it influenced the final answer

OpenDota + LlamaIndex Use Cases

Practical scenarios where LlamaIndex combined with the OpenDota MCP Server delivers measurable value.

01

Hybrid search: combine OpenDota real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query OpenDota to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying OpenDota for fresh data

04

Analytical workflows: chain OpenDota queries with LlamaIndex's data connectors to build multi-source analytical reports

OpenDota MCP Tools for LlamaIndex (18)

These 18 tools become available when you connect OpenDota to LlamaIndex via MCP:

01

get_benchmarks

Compare any player's stats against the broader player base. Requires a hero ID (from list_heroes). Get hero performance benchmarks

02

get_constants

Optionally specify a resource name (e.g. "game_mode", "lobby_type", "lane_role", "patch", "cluster") to get a specific constant set. Get OpenDota constant data

03

get_distributions

Shows how many players are in each bracket (Herald, Guardian, Crusader, Archon, Legend, Ancient, Divine, Immortal). Useful for understanding where a player stands in the overall population. Get MMR and rank distributions

04

get_match

Returns the match duration, game mode, lobby type, league, radiant/dire team compositions, all 10 players' heroes, items, KDA, GPM, XPM, hero damage, tower damage and healing. Also includes draft picks, chat logs and team objectives for professional matches. Get detailed match info

05

get_player

Returns the player's profile picture, rank tier, MMR estimate, total matches, winrate and country. Account IDs are numeric Steam IDs (e.g. 87276347 for Arteezy, 19672354 for SumaiL). Use search to find a player by name first. Get player profile and stats

06

get_player_heroes

Useful for analyzing a player's hero pool and identifying their best heroes. Get a player's performance stats by hero

07

get_player_matches

Each match includes the match ID, hero played, result (win/loss), kills, deaths, assists, duration, game mode, lobby type, league and start time. Sorted by most recent first. Returns thousands of matches for active players. Get a player's match history

08

get_player_recent_matches

Each match includes the match ID, hero played, result, KDA, duration and game mode. Useful for checking a player's current form and recent hero pool. Get a player's recent matches (last 20)

09

get_player_records

Shows the match ID, hero and value for each record. Get a player's personal records

10

get_player_wl

Shows wins and losses for each hero, revealing their strongest and weakest picks. Useful for understanding a player's hero preferences and strengths. Get a player's win/loss record by hero

11

get_records

Supported fields: "kills", "deaths", "assists", "last_hits", "denies", "gold_per_min", "xp_per_min", "hero_damage", "tower_damage", "hero_healing", "level", "duration", "longest_word". Returns the top record holders with match IDs and hero info. Get all-time game records

12

get_team

Returns the team name, tag, logo, rating, win/loss record, player roster, matches played and recent results. Get detailed info for a professional team

13

list_heroes

Returns approximately 124 heroes. Useful for discovering hero IDs to use with other tools. Get the list of all Dota 2 heroes

14

list_leagues

Each league includes its ID, name, tier (premium, professional, amateur), region, start/end dates and logo URL. Useful for discovering tournaments and filtering matches by league. Get the list of professional leagues

15

list_recent_matches

Each match includes the match ID, start time, duration, radiant/dire team average MMR and winner. Returns up to 500 matches. Useful for browsing recent games and finding match IDs to explore. Get recent public matches

16

list_teams

Each team includes its ID, name, tag, logo URL, rating, number of wins/losses and last match time. Sorted by team rating. Useful for discovering pro teams and their IDs. Get the list of professional teams

17

run_explorer_query

Requires a valid SQL query string. Returns query results as an array. Advanced feature for deep data analysis. Example: "SELECT hero_id, count(*) matches FROM player_matches GROUP BY hero_id ORDER BY matches DESC LIMIT 10" Run a custom SQL query via OpenDota Explorer

18

search

Returns matching results with their types and IDs. Useful for finding a player's account ID or a team's ID when you only know their name. Search for players, teams, leagues and heroes

Example Prompts for OpenDota in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex agent to start working with OpenDota immediately.

01

"Search for the player 'Arteezy'."

02

"Show me all Dota 2 heroes."

03

"What are the all-time records for most kills in a single match?"

Troubleshooting OpenDota MCP Server with LlamaIndex

Common issues when connecting OpenDota to LlamaIndex through the Vinkius, and how to resolve them.

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

OpenDota + LlamaIndex FAQ

Common questions about integrating OpenDota MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query OpenDota tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect OpenDota to LlamaIndex

Get your token, paste the configuration, and start using 18 tools in under 2 minutes. No API key management needed.