dota2-coach-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port for the HTTP server (e.g., 8787). Used when running with the HTTP transport. | |
| DOTA2_COACH_CACHE_DIR | No | Path to a persistent cache directory. Defaults to ./cache next to server.js. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_dota2_matchA | Fetch a public Dota 2 match from OpenDota and return a coaching-report-ready JSON summary: result, draft, per-player stats and benchmark percentiles vs. their rank bracket, objectives/teamfight timelines, rank medal, and (with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of misselection or overlap. Its purpose—extracting Dota 2 match data for coaching—is clearly stated.
The single tool uses a clear verb_noun snake_case pattern (analyze_dota2_match). With only one tool, there are no inconsistent naming conventions to compare against.
A single tool is thin for a server framed around coaching, even though this tool is comprehensive. Typical related operations like match discovery or player history are absent, making the surface feel under-scoped.
The tool covers deep single-match extraction including draft, per-player stats, timelines, and optional player deep-dive. It lacks match discovery/list and broader player profile tools, but the core analysis workflow is otherwise usable.