Vlr Stats MCP Server

Most developer tooling work still happens through a UI a human drives. Vlr Stats MCP MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server that provides Claude with access to VLR.gg VALORANT esports data. Built with FastMCP for easy integration with Claude Desktop.

The short version

• get_upcoming_matches — - Get upcoming VALORANT matches with team names, events, and timing
• get_live_matches — - Get matches that are currently LIVE, with the live map score
• get_match_results — - View recent match results with scores and events
• get_match_details — - Full detail for a single match: map veto, per-map scores, and the per-player scoreboard (agent, ACS, K/D/A, ADR)
• get_team_rankings — - Access current team rankings (top 20 by region)
• search_team — - Look up a team's profile: tag, active roster, and staff

The tools it exposes

The server publishes 1 tool. What each one is for:

• Installation — 1. Clone this repository: bash git clone cd vlr-stats-mcp

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Vlr Stats MCP's toolset — Installation — is a fair guide to whether it matches your workflow. It is maintained by okeahdavid; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.