hltv-csgo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HLTV_PROXY | No | Cleaner egress proxy to avoid Cloudflare challenges. | |
| HLTV_COOKIE | No | Valid cf_clearance cookie obtained from a browser on the same IP and User-Agent. | |
| HLTV_CACHE_PATH | No | Path to the SQLite cache file. | |
| HLTV_USER_AGENT | No | Override the User-Agent string sent to HLTV. | |
| HLTV_CURL_BINARY | No | Path to a curl-impersonate binary that mimics Chrome's TLS handshake. |
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 |
|---|---|
| search_hltv_entitiesA | Search HLTV.org for Counter-Strike teams, players, or events. Use this before filtering matches by team when the exact HLTV display name is not already known. |
| list_hltv_matchesA | List upcoming, live, or finished Counter-Strike matches from HLTV.org. Filter by exact team display name, event id, date range, and limit. |
| get_hltv_matchA | Get one HLTV match page's teams, score, event, start time, maps, and streams from an exact match URL returned by list_hltv_matches. |
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 3 tools
Each tool has a distinct purpose: search entities, list matches, and get match details. There is no overlap or ambiguity in their intended use. The descriptions clearly separate the search/filter/get workflow.
All tool names follow a consistent verb_noun pattern: search_hltv_entities, list_hltv_matches, get_hltv_match. The verb clearly indicates the action and the noun indicates the resource, making the pattern predictable.
Three tools is on the lower end but still appropriate for a focused HLTV match data server. The set covers the core workflow of search, list, and detail without feeling excessive. A few more tools could be justified, but the current count is reasonable.
The tools cover the primary workflow: finding entities, listing matches, and retrieving match details. Missing are direct event or player detail endpoints, but search_hltv_entities provides entity discovery. The core match lifecycle appears adequately covered with minor gaps.