About KashRock MCP
KashRock MCP gives esports agents access to tier-scoped match, odds, player, and live-game data across multiple titles. Its tools cover research and rankings as well as live feeds and match intelligence, with capabilities depending on the account tier.
Key features
- 01DFS and sportsbook player props
- 02Consensus lines, gaps, and rankings
- 03Player research, streams, and head-to-head data
- 04Live scores, boxscores, and odds
- 05Match preparation and tournament maps
Use cases
- 01Compare player props and betting lines
- 02Research players, teams, and matchups
- 03Follow live games and odds
- 04Build esports match and betting analysis
MCP support
Exposes KashRock esports data and tools to MCP clients such as Cursor and Claude. Clients can authenticate through login or an API key; available tools are tier-scoped.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx kashrock-mcpKASHROCK_API_KEYSecretKashRock API key. Optional — skips the login tool's Google sign-in flow by supplying an existing key directly.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
46Saved tool list · updated 2w ago
This tool takes no parameters.
Details
From the project READMEkashrock-mcp
Full tier-scoped KashRock esports MCP for Cursor, Claude, and other agents.
Install (effortless)
{
"mcpServers": {
"kashrock": {
"command": "uvx",
"args": ["kashrock-mcp"]
}
}
}
Then say log in to KashRock. Google opens; the agent gets your billed plan.
Requires uv. Optional: KASHROCK_API_KEY skips login.
Local (this repo)
cd mcp && uv sync
Cursor ~/.cursor/mcp.json:
{
"mcpServers": {
"kashrock": {
"command": "uv",
"args": ["run", "--directory", "/ABS/PATH/TO/kashrock/mcp", "kashrock-mcp"],
"env": { "KASHROCK_API_KEY": "kr_…" }
}
}
}
What agents can do
- Board: DFS props (
get_props), DFS+sportsbook player props (get_player_props), media (get_media), player snapshot (get_player_snapshot), consensus lines including DFS Teams (get_lines/get_best_lines), gaps (get_gaps) - Players / research / rankings / streams / H2H
- Builder+: matches, live in-game (
get_live_boxscore/get_live_games/get_live_frame/get_live_odds/get_live_odds_history), live WebSocket (get_live_ws→WS /v6/esports/live/ws), gamelogs, finished vault boxscores (get_boxscore), results, history tape, closing mainlines (get_lines_history) - Match intel:
get_match_prep(CS2, R6, COD, Valorant & Apex team stats, mode/map winrates, map pool/biases, key player matchups, betting insights),get_player_board(CS2 weapons / Valorant agents),get_tournament_maps— pass KashRock slug/kr_match_idonly - Public ids: lists and boxscores emit
kr_match_id,kr_tm_*teams,kr_pl_*players. Lineup includesSTARTERandSUB. Never pass foreign numerics.
Live KDA path: get_live_boxscore("cs2") → pick game_id → get_live_boxscore("cs2", game_id). Sport boards: CS2 money/bomb, LoL gold/towers, Dota gold/roshan when visible, Deadlock gold/CS/level on tournament games. Do not use get_boxscore for mid-map stats (that is finished-match vault + lineup + model fields).
Live WebSocket (Builder+): call get_live_ws for the wss://…/v6/esports/live/ws URL + subscribe ops. Auth with your API key (?api_key= / Bearer / x-api-key). After hello, send {"op":"subscribe","sport":"cs2","game_id":"<id>|*" }. Pushes: snapshot, games_list, frame, boxscore, meta, event, odds. WS traffic does not count against HTTP req/min. MCP returns the contract only — your app holds the socket.
Call whoami, list_capabilities, or suggest_build first. Stacks are not exposed.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.