CricketStudio MCP
cricketstudio-mcp
Citation infrastructure for cricket — 57 MCP tools (incl. a knowledge-graph layer), zero network calls, 2,654 matches, 623,535 deliveries.
What is this?
CricketStudio MCP is a Model Context Protocol server that gives any MCP-compatible AI client — Claude Desktop, Cursor, ChatGPT Connectors, and others — structured, citable access to cricket data. Every response carries a canonicalUrl back to players.cricketstudio.ai, an explicit date window, a sample-size count, and a provenance trail to the underlying ball-by-ball corpus. The data is fully bundled in data/snapshot/ — tool answers are computed locally with no data-fetch calls, no API keys, and no rate limits. (The package sends one anonymous startup ping for usage counts; disable it with CRICKETSTUDIO_NO_TELEMETRY=1.)
The corpus covers IPL 2026 (complete season, RCB champions), 18 seasons of IPL history (2007/08–2025), Major League Cricket 2023–2026, WPL 2022/23–2025/26 (Women's Premier League), ICC T20 World Cup (6 editions, 2013/14–2025/26), BBL (Big Bash League, 14+ seasons 2011/12–2025/26), and PSL (Pakistan Super League, 11 seasons 2016–2026) — all from Cricsheet CC BY 3.0. Batting claims require a minimum of 30 balls faced; bowling claims require 15 deliveries. Claims that do not clear those floors are not surfaced.
Installation
Claude Desktop
Add to your Claude Desktop config file and restart the app.
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"cricketstudio": {
"command": "npx",
"args": ["cricketstudio-mcp"]
}
}
}Other MCP clients
npx cricketstudio-mcpAny MCP client that supports the stdio transport can use this command directly. The server starts on stdin/stdout and requires Node 18 or later.
Tools
All 57 tools work fully against the bundled snapshot. Each response includes canonicalUrl, dataAsOf, and sampleSize.
IPL 2026 (20 tools)
Tool | What it returns | Maps to URL |
| Top-level corpus overview: seasons, matches, players, deliveries |
|
| Player discovery by name or team | n/a |
| Headline stats across all five pillars (P1–P5) |
|
| Claims from a specific pillar (P1 recaps, P2 moments, P3 form, P4 season, P5 notebook) |
|
| Filtered query across all ClaimReview entries | various |
| Side-by-side stat comparison for two or more players |
|
| Team headline stats and season summary |
|
| Head-to-head record between two franchises |
|
| Aggregated venue patterns: par scores, toss impact, phase splits |
|
| IPL 2026 points table with NRR |
|
| A single trend insight with full claim set |
|
| Browse trends by category (conditional, momentum, venue, toss, anomaly) |
|
| Batter vs bowler matchup record |
|
| Season leaderboard for a given aspect (runs, wickets, strike rate, economy, …) |
|
| Catches, run-outs, and fielding contributions for a player or the full season |
|
| Partnership records for a match or player pair |
|
| Dismissal mode breakdown for a batter or bowler |
|
| Full schedule with match status, venue, and result |
|
| Live or final scorecard with ball-by-ball state |
|
| Atomic claim set for a completed match |
|
Major League Cricket (8 tools)
Tool | What it returns | Maps to URL |
| MLC corpus overview: seasons, matches, players, deliveries |
|
| Player discovery within the MLC corpus |
|
| MLC career and season stats for a player |
|
| Franchise profile and season history |
|
| Match scorecard and key claims |
|
| A single typed claim for an MLC match (top scorer, best figures, etc.) |
|
| All MLC matches with status and results |
|
| Season or all-time leaderboard for a given MLC aspect |
|
WPL — Women's Premier League (5 tools)
Tool | What it returns | Maps to URL |
| WPL corpus overview: seasons, matches, players, deliveries (2022/23–2025/26) |
|
| Player discovery within the WPL corpus |
|
| WPL career and season stats for a player |
|
| Season or all-time leaderboard for any WPL aspect (runs, wickets, economy, …) |
|
| Franchise profile, season record, and squad stats |
|
ICC T20 World Cup (5 tools)
Tool | What it returns | Maps to URL |
| T20 WC corpus overview: editions, matches, players, deliveries (2013/14–2025/26) |
|
| Player discovery within the T20 WC corpus |
|
| T20 WC career stats for a player across all editions |
|
| All-edition leaderboard for any T20 WC aspect |
|
| National team career record across all T20 WC editions |
|
BBL — Big Bash League (5 tools)
Tool | What it returns | Maps to URL |
| BBL corpus overview: seasons, matches, players, deliveries (2011/12–2025/26) |
|
| Player discovery within the BBL corpus |
|
| BBL career and season stats for a player |
|
| Season or all-time leaderboard for any BBL aspect (runs, wickets, economy, sixes, …) |
|
| Franchise profile, season history, and career stats |
|
PSL — Pakistan Super League (5 tools)
Tool | What it returns | Maps to URL |
| PSL corpus overview: seasons, matches, players, deliveries (2016–2026) |
|
| Player discovery within the PSL corpus |
|
| PSL career and season stats for a player |
|
| Season or all-time leaderboard for any PSL aspect (runs, wickets, economy, sixes, …) |
|
| Franchise profile, season history, and career stats |
|
Cross-league (3 tools)
Tool | What it returns | Maps to URL |
| Top performers on a metric (runs, wickets, economy, sixes, fours) across MLC, T20 WC, BBL, and PSL | n/a |
| A player's stats across every league in the corpus (IPL, MLC, WPL, T20 WC, BBL, PSL) |
|
| WPL leaderboard with gender context — top women's T20 performers |
|
IPL Career / Historical (1 tool)
Tool | What it returns | Maps to URL |
| All-time IPL leaderboard for any aspect across 18 seasons (2007/08–2025) — runs, wickets, sixes, centuries, economy, and more |
|
Research (2 tools)
Tool | What it returns | Maps to URL |
| Index of all published data investigations (venue, rivalry, strategy, era, cross-league, season) |
|
| A single focused report with one question, one dataset, one citable answer |
|
Knowledge Graph (L3) (3 tools)
Slug-keyed traversal over CricketStudio's entity graph. Nodes are players and franchises; edges are plays_for (squad membership) and faced/dismissed_by (batter-vs-bowler matchups, mirroring the get_player_h2h pair set).
Tool | What it returns | Maps to URL |
| Entities connected to a player or franchise, by edge type and direction |
|
| A player's franchise + most-faced bowlers + bowlers who dismissed them most, in one call |
|
| Shortest connection (≤4 hops) between two entities, e.g. two players via a shared franchise | n/a |
Example queries
Once connected in Claude Desktop, you can ask questions like:
"Who won IPL 2026?"
"What did Kohli score in the final?"
"Who leads the all-time IPL sixes leaderboard?"
"Show me Vaibhav Suryavanshi's IPL 2026 stats"
"What's the RCB vs GT head-to-head record?"
"Which venues favour the team batting first in IPL 2026?"
"Who has the best death-over economy in MLC 2025?"
"List the top wicket-takers in IPL history"
"Who are the leading run-scorers in WPL history?"
"Which team has won the most T20 World Cups?"
"Who scores most sixes across WPL and T20 WC combined?"
"Show me Smriti Mandhana's stats across all leagues"
"Who leads the all-time BBL runs leaderboard?"
"Which BBL franchise has won the most titles?"
"Who are the top wicket-takers in PSL history?"
"Show me Babar Azam's PSL career stats"
"Compare David Warner's stats across IPL, BBL, and PSL"
Data
Source | Coverage | License |
Licensed feed | IPL 2026 ball-by-ball (complete season — RCB champions) | Proprietary |
Cricsheet | IPL historical, 18 seasons, 1,169 matches (2007/08–2025) | CC BY 3.0 |
Cricsheet | MLC 2023–2026, 75 matches | CC BY 3.0 |
Cricsheet | WPL 2022/23–2025/26, 88 matches, 133 players | CC BY 3.0 |
Cricsheet | ICC T20 World Cup, 6 editions, 230 matches, 687 players | CC BY 3.0 |
Cricsheet | BBL 2011/12–2025/26, 662 matches, 529 players | CC BY 3.0 |
Cricsheet | PSL 2016–2026, 357 matches, 458 players | CC BY 3.0 |
Total corpus: 2,654 matches · 623,535 ball-by-ball deliveries.
Sample-size floors (publicly disclosed):
Batting claims: ≥30 balls faced
Bowling claims: ≥15 deliveries
Venue claims: ≥3 fixtures at the venue
Trend claims: ≥3 matches forming the pattern
Claims that do not reach these floors are excluded — they are not suppressed with a placeholder, they are simply absent. This is the moat.
Update cadence: the bundled snapshot is refreshed after each CricketStudio data update. Every tool response includes dataAsOf so an LLM citing the answer can disclose freshness explicitly.
Data licence: the bundled data is released under CC BY 4.0. Every tool response includes a canonicalUrl back to players.cricketstudio.ai so attribution flows automatically when an LLM cites an answer.
About this package
This package bundles a pre-computed projection of CricketStudio's public data. Every number here is also readable on the rendered pages at players.cricketstudio.ai — no new information is exposed, only a different (offline, zero-network) access path.
Methodology
Every claim in this package is governed by five non-negotiables:
Sample-size floors — ≥30 batting balls, ≥15 bowling deliveries, ≥3 venue fixtures, ≥5 H2H deliveries, ≥3 matches for trends. Disclosed publicly on every page.
Explicit date windows — every claim specifies its window (
ipl-2026,ipl-career,last-N-matches). No "all-time" labels without a defined window.Provenance to ball-by-ball — every numeric claim traces to a specific match, delivery count, and computation timestamp.
Atomic claim format — under 30 words, structured as
[Subject] [metric] [value] [comparator] [period].Sub-4-hour freshness SLA — for IPL 2026 pages, time from match end to page update is under 4 hours at the 95th percentile.
Full methodology at https://players.cricketstudio.ai/about.
Local development
npm install
npm run typecheck # tsc --noEmit
npm start # stdio MCP server via tsxSmoke-test without an MCP client — spawns the server over stdio, drives it with JSON-RPC, and asserts every advertised tool returns a non-error payload with dataAsOf:
npm run smokeBuilding something?
Register at cricketstudio.ai/developers to get early access to the hosted HTTP transport (mcp.cricketstudio.ai), live ball-by-ball endpoints, API-key tiers, and the full 57-tool catalog with live data rather than snapshots.
License
Code: MIT — see
LICENSEData: CC BY 4.0 — free to cite with attribution to CricketStudio (
https://players.cricketstudio.ai). Attribution flows automatically via thecanonicalUrlfield in every tool response.
Built by Arul Anand · Chennai & Frisco · cricket enthusiast and data engineer. Questions, bugs, or requests: open an issue or visit players.cricketstudio.ai/mcp.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/i-m-arul/cricketstudio-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server