Valorant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_DIR | No | Directory where completed matches are cached permanently. | ~/.cache/valorant-mcp |
| HENRIK_API_KEY | Yes | Your Henrik API key, required to access the Henrik API. | |
| HENRIK_BASE_URL | No | Base URL for the Henrik API. Set to https://beta.api.henrikdev.xyz/valorant for 4.10 beta fields. | https://api.henrikdev.xyz/valorant |
| VALORANT_REGION | No | Valorant region. Valid values: na, eu, ap, kr, latam, br. | na |
| VALORANT_PLATFORM | No | Valorant platform. Valid values: pc or console. | pc |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_player_profileA | Account info plus ranked state: current rank/RR/elo, last RR change, peak rank, rank protection, and season-by-season results. |
| get_performance_reportA | Broad analysis of a player's recent matches. Start here for "how am I doing / what are my patterns". Sections:
|
| compare_periodsA | Compare the most recent |
| get_rr_historyA | Competitive RR change per match, joined with how the player performed in that match (agent, KDA, ACS, KAST, first kills/deaths). Use it to see which kinds of games gain or lose RR, and RR performance bonuses/penalties. |
| get_match_historyA | List matches, one compact row each: map, agent, result, score, KDA, ACS, ADR, HS%, KAST,
first kills/deaths, ACS rank on team, party size. Defaults to the last 10; pass a larger
|
| get_match_detailsA | Full details of one match.
|
| get_benchmarksA | Judge whether the player's numbers are good or bad by comparing them with the other 9 players in the same matches (so rank is controlled for):
|
| get_teamplay_reportA | Spacing and trading, from every player's position at each kill:
|
| get_site_reportA | Team-level site play per map: on attack, plant rate, which site you plant and the post-plant win % on each; on defense, which site the enemy plants and your retake/hold win %; plus win % in rounds with no plant. Use for "which site should we hit on Bind" or "are we bad at retakes". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| coach_review | Structured coaching review of a player's recent games: what to keep, change, and try. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| glossary | Definitions of every metric these tools return. |
TDQS
Scored across 9 tools
The descriptions are rich and include 'use for' hints, but several tools overlap: get_performance_report bundles positioning/context/economy sections that are also the focus of get_teamplay_report, get_site_report, and get_benchmarks. An agent may struggle to decide between the broad performance report and the specialized reports for questions like 'why do I die alone'.
Eight of nine tools follow a clear get_<noun>_<type> pattern (get_player_profile, get_match_history, get_teamplay_report, etc.). compare_periods is the lone deviation, breaking the verb_noun convention used everywhere else, but it remains readable.
Nine tools is well within the ideal 3-15 range and each targets a distinct analysis surface (profile, history, details, benchmarks, teamplay, site, RR). Nothing feels redundant enough to cut, and the count is not so large as to overwhelm an agent.
The surface covers the full analytics lifecycle: account/rank (profile), match listing and single-match detail, RR trends, period comparison, benchmarking, plus teamplay and site-specific analyses. For a read-only performance analytics domain this is comprehensive with no obvious dead ends.