Valorant MCP Server
Related Servers
Alternatives to Valorant MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Valorant esports analytics that exposes structured metrics and database query tools, enabling AI-assisted match analysis, player profiling, scouting reports, and coaching insights.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server for Valorant esports that enables querying match schedules, live results, AI-powered analysis, and setting reminders.-
- AlicenseNot gradedqualityBmaintenanceProvides VALORANT account and match data through HenrikDev's API. Enables querying profile, recent competitive matches, and match details.1MIT
- AlicenseBqualityBmaintenanceMCP server exposing 30 tools for League of Legends player analysis, match review, and training-plan generation.3517 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable assistants to perform post-match Valorant analysis by inspecting stats, reviewing rounds and deaths, rendering tactical maps, and finding community lineups from a Riot ID or match link.MIT
- AlicenseNot gradedqualityCmaintenanceProvides structured Valorant esports analytics data and metrics through MCP, including match analysis, player profiling, scouting reports, and ad-hoc SQL queries. Enables AI models to generate accurate coaching insights from pre-computed analytics tables.Apache 2.0
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.