Allows accessing OpenDota API data to retrieve real-time Dota 2 statistics, match data, player information, hero statistics, professional players and teams information.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@OpenDota MCP Server show me the recent matches for player ID 8674590"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server implementation for accessing OpenDota API data. This server enables LLMs and AI assistants to retrieve real-time Dota 2 statistics, match data, player information, and more through a standard interface.
Access player profiles, statistics, and match history
Retrieve detailed match information
Look up professional players and teams
Get hero statistics and rankings
Search for players by name
And more!
Related MCP server: MonkeyType MCP Server
To install OpenDota API Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @asusevski/opendota-mcp-server --client claude# Clone the repository
git clone https://github.com/asusevski/opendota-mcp-server.git
cd opendota-mcp-server
# Option 1: Automated setup (works with bash, zsh, and other shells)
./scripts/setup_env.sh
# Option 2: Manual installation with uv
uv add pyproject.toml
# For development dependencies
uv pip install -e ".[dev]"(Optional but recommended) Create an OpenDota API key at https://www.opendota.com/api-keys
Set your API key as an environment variable:
export OPENDOTA_API_KEY=your_api_key_herepython -m src.opendota_server.serverFollow this: https://modelcontextprotocol.io/quickstart/user
If you use WSL, assuming you have cloned the repo and set up the python environment, this is how I wrote the claude_desktop_config.json:
{
"mcpServers": {
"opendota": {
"command": "wsl.exe",
"args": [
"--",
"bash",
"-c",
"cd ~/opendota-mcp-server && source .venv/bin/activate && python src/opendota_server/server.py"
]
}
}
}python -m src.clientget_player_by_id - Retrieve player information by account ID
get_player_recent_matches - Get recent matches for a player
get_match_data - Get detailed data for a specific match
get_player_win_loss - Get win/loss statistics for a player
get_player_heroes - Get a player's most played heroes
get_hero_stats - Get statistics for heroes
search_player - Search for players by name
get_pro_players - Get list of professional players
get_pro_matches - Get recent professional matches
get_player_peers - Get players who have played with a specified player
get_heroes - Get list of all Dota 2 heroes
get_player_totals - Get player's overall stats totals
get_player_rankings - Get player hero rankings
get_player_wordcloud - Get most common words used by player in chat
get_team_info - Get information about a team
get_public_matches - Get recent public matches
get_match_heroes - Get heroes played in a specific match
MIT
Get list of all Dota 2 heroes.
Returns:
List of all heroes with basic information
Inputs: no named parameters. Returns: result
Get statistics for heroes.
Args:
hero_id: Optional hero ID to get stats for a specific hero
Returns:
Hero statistics including win rates by skill bracket
Inputs: hero_id. Returns: result
Get detailed data for a specific match.
Args:
match_id: ID of the match to retrieve
Returns:
Detailed match information including players, scores, and stats
Inputs: match_id (required). Returns: result
Get heroes played in a specific match.
Args:
match_id: ID of the match to retrieve
Returns:
List of heroes played by each player in the match
Inputs: match_id (required). Returns: result
Get a player's information by their account ID.
Args:
account_id: The player's Steam32 account ID
Returns:
Player information including rank, matches, and statistics
Inputs: account_id (required). Returns: result
Get a player's most played heroes.
Args:
account_id: Steam32 account ID of the player
limit: Number of heroes to retrieve (default: 5)
Returns:
List of most played heroes with stats
Inputs: account_id (required), limit. Returns: result
Get players who have played with the specified player.
Args:
account_id: Steam32 account ID of the player
limit: Number of peers to retrieve (default: 5)
Returns:
List of players frequently played with
Inputs: account_id (required), limit. Returns: result
Get player hero rankings.
Args:
account_id: Steam32 account ID of the player
Returns:
Player's hero rankings
Inputs: account_id (required). Returns: result
Get recent matches played by a player.
Args:
account_id: Steam32 account ID of the player
limit: Number of matches to retrieve (default: 5)
Returns:
List of recent matches with details
Inputs: account_id (required), limit. Returns: result
Get player's overall stats totals.
Args:
account_id: Steam32 account ID of the player
Returns:
Summary of player's total stats
Inputs: account_id (required). Returns: result
Get win/loss statistics for a player.
Args:
account_id: Steam32 account ID of the player
Returns:
Win/loss record
Inputs: account_id (required). Returns: result
Get most common words used by player in chat.
Args:
account_id: Steam32 account ID of the player
Returns:
List of player's most frequently used words
Inputs: account_id (required). Returns: result
Get recent professional matches.
Args:
limit: Number of matches to retrieve (default: 5)
Returns:
List of recent professional matches
Inputs: limit. Returns: result
Get list of professional players.
Args:
limit: Number of players to retrieve (default: 10)
Returns:
List of professional players
Inputs: limit. Returns: result
Get recent public matches.
Args:
limit: Number of matches to retrieve (default: 5)
Returns:
List of recent public matches
Inputs: limit. Returns: result
Get information about a team.
Args:
team_id: Team ID
Returns:
Team information
Inputs: team_id (required). Returns: result
Search for players by name.
Args:
query: Name to search for
Returns:
List of matching players
Inputs: query (required). Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 17 tools
Most tools have distinct purposes targeting different resources (heroes, matches, players, teams, pro scene). However, some player-focused tools like get_player_heroes and get_player_rankings could potentially overlap in retrieving hero-related player data, though descriptions clarify their specific focuses.
All tools follow a consistent verb_noun pattern with get_ prefix and snake_case throughout. The naming is highly predictable and readable, making it easy to understand each tool's function at a glance.
17 tools is slightly high but reasonable for a comprehensive Dota 2 statistics server. The count supports detailed player analysis, match data, hero stats, and professional scene coverage without being overwhelming for the domain scope.
The toolset provides excellent coverage of the OpenDota API domain with comprehensive player analysis (stats, matches, heroes, peers, rankings), match data (public, pro, detailed), hero statistics, team info, and search functionality. No obvious gaps exist for typical agent workflows.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for Studex tools, notifications, and profile integrations
The official Model Context Protocol server for Ambee. It gives any MCP-compatible AI assistant — Claude, ChatGPT, Cursor, VS Code, Ollama, and more direct access to live air quality, pollen, and weather data. To get started, including information on signing up and obtaining your Ambee key, check out the Ambee documentation on https://docs.ambeedata.com
