Valorant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VALORANT_API_KEY | Yes | Your Valorant API key from HenrikDev API |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_detailsA | Get account details for a Valorant player. Essential tool for getting PUUID and account information. Args: name: Player's in-game name tag: Player's tag region: Region code (ap, na, eu, kr, br, latam) Returns: PUUID, account level, player card, region info |
| get_match_history_by_nameA | Get recent match history for a player. Returns matches across all game modes with detailed stats. Args: name: Player's in-game name tag: Player's tag region: Region code (ap, na, eu, kr, br, latam) size: Number of matches (default: 10, max: 20) Returns: List of matches with kills, deaths, assists, agents, maps, scores |
| get_match_detailsA | Get detailed information about a specific match. Provides comprehensive match data including all players' stats. Args: match_id: Match identifier region: Region code (ap, na, eu, kr, br, latam) Returns: Match details with all players, rounds, scores |
| get_mmr_details_by_nameA | Get current MMR and rank for a player. Provides current competitive standing. Args: name: Player's in-game name tag: Player's tag region: Region code (ap, na, eu, kr, br, latam) Returns: Current rank, ELO, RR, last game MMR change |
| get_mmr_history_by_nameA | Get MMR history with match IDs and maps. Essential for competitive analysis - includes match IDs for each game! Args: name: Player's in-game name tag: Player's tag region: Region code (ap, na, eu, kr, br, latam) size: Number of history entries (default: 10, max: 20) Returns: MMR history with match IDs, maps, rank changes, dates |
| get_lifetime_matches_by_nameA | Get lifetime match statistics (different API endpoint). Provides aggregate lifetime stats and match history. Args: name: Player's in-game name tag: Player's tag region: Region code (ap, na, eu, kr, br, latam) mode: Optional game mode filter map_filter: Optional map filter page: Page number (default: 1) size: Matches per page (default: 20) Returns: Lifetime stats and match list |
| get_leaderboardA | Get the competitive leaderboard for a region. Shows top players in region/season. Args: region: Region code (ap, na, eu, kr, br, latam) season: Season identifier (default: e8a1) Returns: List of top players with rankings and ratings |
| get_contentC | Get game content (agents, maps, weapons). Essential for understanding game elements. Args: region: Region code (ap, na, eu, kr, br, latam) Returns: All agents, maps, and game content |
| get_statusA | Get Valorant service status. Checks for maintenance and incidents. Args: region: Region code (ap, na, eu, kr, br, latam) Returns: Service status, maintenance windows, incidents |
| set_api_keyA | Set the API key for Valorant API requests. Required for authentication. Args: api_key_input: Your HenrikDev API key Returns: Confirmation message |
| get_detailed_competitive_analysisA | Get comprehensive competitive analysis by combining MMR history + match details. This is the most powerful tool for competitive insights. Combines two different API endpoints to correlate performance with MMR changes. Args: name: Player's in-game name tag: Player's tag region: Region code (ap, na, eu, kr, br, latam) match_count: Number of matches to analyze (default: 10, max: 20) Returns: Detailed competitive matches with performance + MMR correlation |
| find_leaderboard_positionA | Find a player's position on the competitive leaderboard. Searches leaderboard and provides position + nearby players. Only works for Immortal 3+ players. Args: name: Player's in-game name tag: Player's tag region: Region code (ap, na, eu, kr, br, latam) season: Season identifier (default: e8a1) Returns: Leaderboard position, rank, nearby players |
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 12 tools
Most tools target distinct resources/actions. There is slight overlap between get_match_history_by_name and get_lifetime_matches_by_name, but descriptions clarify the difference (recent vs lifetime aggregate). Otherwise, tools are clearly distinct.
Predominantly uses get_<resource>_<detail> pattern with consistent snake_case. Minor deviations with set_api_key and find_leaderboard_position, but overall the pattern is predictable.
12 tools is well-scoped for a Valorant stats API, covering accounts, matches, MMR, leaderboard, content, status, and auth. No redundancy.
The tool surface is comprehensive for read-only stat retrieval: account, recent/lifetime matches, match details, MMR details/history, leaderboard access, content, status, and a composite analysis tool. No obvious dead ends; all tools connect (e.g., MMR history returns match IDs for match details).