KashRock MCP — esports MCP server for Claude Code: install guide
Gives your agent esports props, odds lines, live scores and player stats it can query on its own instead of you tabbing through dashboards.
claude mcp add kashrock-mcp -e KASHROCK_API_KEY=<KASHROCK_API_KEY> -- uvx kashrock-mcpWhat KashRock MCP does
This server links an agent to KashRock's esports data: DFS props, player props for DFS and sportsbook, consensus lines, media and player snapshots. Player research, rankings, streams and head-to-head lookups sit alongside those calls. Builder+ accounts reach live in-game stats, stored game logs, results and closing mainlines.
Match prep runs per title — CS2, R6, COD, Valorant and Apex — with team stats, mode and map winrates, map pool, key player matchups. Player boards cover CS2 weapons and Valorant agents. IDs come back in KashRock's own format (kr_match_id, kr_tm_*, kr_pl_*); foreign numeric IDs get rejected, so pass the slug or the kr_match_id you already have.
The launcher is uvx kashrock-mcp, and it needs uv installed. No API key is fine: the server opens a Google sign-in and picks up the plan on that account. Setting KASHROCK_API_KEY skips the login. Live WebSocket access is Builder+ too — get_live_ws hands back the URL and subscribe operations, while the socket itself lives in your app. It does not count against the HTTP request limit. Start with whoami or list_capabilities. For stats during a map use get_live_boxscore; get_boxscore only covers finished matches.
What it helps with
- pull props and lines ahead of a match
- read live score and stats mid-map
- compare team winrates on specific maps
- trace closing lines across a tournament
- stream live match events into your own app
Example prompts for the agent
- List today's CS2 lines and flag any gaps between books
- Pull the live boxscore for the current game and break down the economy
- Prep a match report: map pool, winrates and key matchups
How to install KashRock MCP
Platform CLI
claude mcp add kashrock-mcp -e KASHROCK_API_KEY=<KASHROCK_API_KEY> -- uvx kashrock-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from kashrock-mcp <command>
Platform CLI
codex mcp add kashrock-mcp --env KASHROCK_API_KEY=<KASHROCK_API_KEY> -- uvx kashrock-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from kashrock-mcp <command>
Config file
{
"mcpServers": {
"kashrock-mcp": {
"command": "uvx",
"args": [
"kashrock-mcp"
],
"env": {
"KASHROCK_API_KEY": "<KASHROCK_API_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from kashrock-mcp <command>
Config file
{
"servers": {
"kashrock-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"kashrock-mcp"
],
"env": {
"KASHROCK_API_KEY": "<KASHROCK_API_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from kashrock-mcp <command>
Platform CLI
gemini mcp add -e KASHROCK_API_KEY=<KASHROCK_API_KEY> kashrock-mcp uvx kashrock-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from kashrock-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about KashRock MCP
How do I install KashRock MCP in Claude Code?
Run claude mcp add kashrock-mcp -e KASHROCK_API_KEY=<KASHROCK_API_KEY> -- uvx kashrock-mcp. The flag-style form works too: claude mcp add --env KASHROCK_API_KEY=<KASHROCK_API_KEY> --transport stdio kashrock-mcp -- uvx kashrock-mcp.
What does KashRock MCP do?
It exposes KashRock's esports feed to your agent: props, lines, live stats, game logs and match prep. The agent calls the methods it needs and folds the answers into a report or your own pipeline.
What does the server need to run?
The uv tool, since the server starts as uvx kashrock-mcp. KASHROCK_API_KEY is optional — leave it out and the server prompts a Google sign-in tied to your plan.
