Valorant MCP Server
Provides access to Valorant game data, including player information, match history, MMR, leaderboards, game content (agents, maps, weapons), and service status, using the HenrikDev unofficial Valorant API.
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., "@Valorant MCP Server show MMR for player 'Scream' in EU"
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.
Valorant MCP Server
A Model Context Protocol (MCP) server that provides access to Valorant game data using the unofficial Valorant API.
Features
Player Information: Get account details, MMR, and match history
Match Data: Detailed match information and statistics
Game Content: Agents, maps, weapons, and other game assets
Service Status: Check Valorant service status and maintenance
Leaderboards: Competitive rankings and leaderboards
Related MCP server: MCP Riot Server
Prerequisites
Python 3.11 or higher
A Valorant API key from HenrikDev API
Internet connection for API requests
Installation
Option 1: Run via uvx (Recommended)
No local environment setup required. uvx runs the packaged console script directly.
# Install UV if you don't have it
curl -LsSf https://astral.sh/uv/install.sh | sh
# Run from GitHub (replace with your repo URL)
uvx --from git+https://github.com/<your-username>/valorant-mcp-server.git valorant-mcp-server
# Windows (PowerShell)
uvx --from git+https://github.com/<your-username>/valorant-mcp-server.git valorant-mcp-serverOptionally set an API key in the environment first (or use the set_api_key tool at runtime):
export VALORANT_API_KEY="your_api_key_here"
uvx --from git+https://github.com/<your-username>/valorant-mcp-server.git valorant-mcp-serverOption 2: Local UV/Pip environment
# Clone and setup
git clone https://github.com/<your-username>/valorant-mcp-server.git
cd valorant-mcp-server
# With UV
uv venv && . .venv/bin/activate # Windows: .venv\Scripts\activate
uv pip install -r requirements.txt
# Or with pip
python -m venv .venv && . .venv/bin/activate
pip install -r requirements.txt
# Environment
cp env.example .env # Windows: copy env.example .env
# Edit .env and add your VALORANT_API_KEYUsage
Running the Server
# Recommended: uvx from git
uvx --from git+https://github.com/<your-username>/valorant-mcp-server.git valorant-mcp-server
# Locally (if you've installed deps)
python server.pyNote: The server will start and wait for MCP client connections. It will show a warning if no API key is set, but you can still use the set_api_key tool to configure it at runtime.
Using with MCP Clients
Claude Desktop
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"valorant": {
"command": "uvx",
"args": ["--from", "git+https://github.com/<your-username>/valorant-mcp-server.git", "valorant-mcp-server"],
"env": {
"VALORANT_API_KEY": "your_api_key_here"
}
}
}
}Cline (VS Code Extension)
Add to your Cline configuration:
{
"mcpServers": {
"valorant": {
"command": "uvx",
"args": ["--from", "git+https://github.com/<your-username>/valorant-mcp-server.git", "valorant-mcp-server"],
"env": {
"VALORANT_API_KEY": "your_api_key_here"
}
}
}
}Generic MCP Client
Use the packaged command with uvx:
uvx --from git+https://github.com/<your-username>/valorant-mcp-server.git valorant-mcp-serverAvailable Tools
get_account_details(name, tag, region="na"): Basic account info (PUUID, level, card, region).
get_match_history_by_name(name, tag, region="na", size=10): Recent matches with per-game stats.
get_match_details(match_id, region="na"): Full details for a specific match.
get_mmr_details_by_name(name, tag, region="na"): Current competitive tier, ELO, RR.
get_mmr_history_by_name(name, tag, region="na", size=10): Competitive MMR history with match IDs.
get_lifetime_matches_by_name(name, tag, region="na", mode=None, map_filter=None, page=1, size=20): Aggregate lifetime stats and list of matches.
get_leaderboard(region="na", season="e8a1"): Top players for a region/season.
get_content(region="na"): Agents, maps, and other content.
get_status(region="na"): Service status and incidents.
set_api_key(api_key_input): Set HenrikDev API key at runtime.
get_detailed_competitive_analysis(name, tag, region="na", match_count=10): Correlate MMR history with match stats.
find_leaderboard_position(name, tag, region="na", season="e8a1"): Locate a player on the leaderboard (Immortal 3+).
Testing
You can validate connectivity by launching the server via uvx and connecting from your MCP client (Claude Desktop/Cline/Cursor). Use the get_status and get_content tools to confirm responses.
Configuration
Environment Variables
VALORANT_API_KEY: Your Valorant API key (required)
API Key Setup
You can set your API key in two ways:
Environment Variable: Set
VALORANT_API_KEYin your environmentRuntime: Use the
set_api_keytool to configure it at runtime
Project Structure
valorant-mcp-server/
├── server.py # MCP server implementation (FastMCP)
├── pyproject.toml # Package metadata + console script
├── requirements.txt # Python dependencies (for local installs)
├── env.example # Environment variables template
├── mcp-client-configs.md # Client configuration examples
├── TOOLS_DOCUMENTATION.md # Detailed tool docs
├── LICENSE # MIT License
├── .gitignore # Git ignore file
└── README.md # This fileAPI Integration
This server uses:
HenrikDev API - The core API service for Valorant data
Direct HTTP Requests - Python requests library for API calls
FastMCP - MCP framework
Error Handling
The server includes comprehensive error handling for:
Invalid API keys
Rate limiting
Network errors
Invalid player names or regions
Service unavailability
All errors are logged and returned in a structured format.
Development
Adding New Tools
To add new Valorant API endpoints:
Create a new function decorated with
@mcp.tool()Add proper error handling with try/catch blocks
Use the global
valo_apiinstanceReturn structured data using Pydantic models
Update this README with the new tool documentation
Code Quality
# Install development tools
pip install black isort mypy flake8
# Format code
black server.py test_server.py
isort server.py test_server.py
# Type checking
mypy server.py
# Linting
flake8 server.py test_server.pyContributing
Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request
License
This project is licensed under the MIT License.
Acknowledgments
Available Tools
12 toolsfind_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
Inputs: tag (required), name (required), region, season. Returns: object
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
Inputs: tag (required), name (required), region. Returns: object
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
Inputs: region. Returns: object
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
Inputs: tag (required), name (required), region, match_count. Returns: object
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
Inputs: region, season. Returns: object
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
Inputs: tag (required), name (required), mode, page, +3 more. Returns: object
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
Inputs: match_id (required), region. Returns: object
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
Inputs: tag (required), name (required), size, region. Returns: object
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
Inputs: tag (required), name (required), region. Returns: object
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
Inputs: tag (required), name (required), size, region. Returns: object
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
Inputs: region. Returns: object
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
Inputs: api_key_input (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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).
Maintenance
Related MCP Connectors
VALORANT reference data MCP (valorant-api.com).
BGG MCP provides access to the BoardGameGeek API through the Model Context Protocol, enabling retr…
Model Context Protocol server for Studex tools, notifications, and profile integrations
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides Formula One data and statistics through a Model Context Protocol interface, allowing users to access race calendars, session results, driver statistics, telemetry data, and championship standings.811MIT
- AlicenseBqualityDmaintenanceA community-developed Model Context Protocol server that integrates with the Riot Games API to provide League of Legends data, enabling AI assistants to retrieve player information, ranked stats, champion mastery, and match summaries through natural language queries.527MIT

OP.GG MCP Serverofficial
AlicenseBqualityCmaintenanceA Model Context Protocol implementation that enables AI agents to retrieve game data from OP.GG for League of Legends, Teamfight Tactics, Valorant, and esports through function calling.24106MIT- AlicenseBqualityDmaintenanceEnables access to MLB Stats API data including game schedules, results, team information, and player lookups with fuzzy matching support through the Model Context Protocol.37MIT