KashRock MCP

com.kashrockPublished by kashrock.comv0.6.6Updated Oct 24, 2026

Esports props, odds, live scores, and player stats across 8 titles for agents.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

KashRock MCP gives an AI assistant tier-scoped access to esports props, odds, live scores, match intel and player stats across 8 titles.

What you can do
Retrieve DFS and sportsbook player props, consensus lines, best lines and gaps, plus media and player snapshots for the board workflow. Look up players, research, rankings, streams and head-to-head records. Pull match intel such as team stats, map win rates, map pools and key player matchups for CS2, R6, COD, Valorant and Apex. Follow live games with boxscores, frames, odds and odds history, and get the live WebSocket contract for subscribing to pushes. Check finished-match boxscores, results, history and closing mainlines, and call whoami, list_capabilities or suggest_build to see what the current plan allows.
When to use it
Useful when you want an assistant to research esports betting props and odds, prepare for a specific match, or follow live in-game data across the supported titles without leaving the chat.
Requirements
Runs locally over stdio with uvx (uv required). A KashRock account and billed plan are needed; the login tool opens Google sign-in, or an existing key can be supplied through the KASHROCK_API_KEY environment variable. Network access to KashRock is required.
Before you install
Access is tier-scoped and tied to a billed plan, so usage may cost money. The login flow opens Google sign-in in a browser. The optional KASHROCK_API_KEY secret is passed in the environment and is also used to authenticate the live WebSocket. The server returns the WebSocket contract only; your own app holds the socket.

Installation

In SourceWeft

  1. Open KashRock MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

kashrock-mcp

Full tier-scoped KashRock esports MCP for Cursor, Claude, and other agents.

Install (effortless)

json
{  "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)

bash
cd mcp && uv sync

Cursor ~/.cursor/mcp.json:

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_id only
  • Public ids: lists and boxscores emit kr_match_id, kr_tm_* teams, kr_pl_* players. Lineup includes STARTER and SUB. 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.

Docs: https://www.kashrock.com/mcp

App SDKs (not MCP): pip install kashrock · Python · JS

Source: README.md at commit 084f271

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.6.6LatestSep 19, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts