CricketStudio MCP Server

29 MCP tools for IPL 2026, IPL historical (18 seasons), and Major League Cricket. No API key. Exposed over MCP by the cricketstudio mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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

Its toolset

Everything the assistant can do here goes through one of these:

• get_dataset_summary — Top-level corpus overview: seasons, matches, players, deliveries
• search_players — Player discovery by name or team
• get_player_profile — Headline stats across all five pillars (P1–P5)
• get_player_pillar — Claims from a specific pillar (P1 recaps, P2 moments, P3 form, P4 season, P5 notebook)
• list_atomic_claims — Filtered query across all ClaimReview entries
• compare_players — Side-by-side stat comparison for two or more players
• get_team_profile — Team headline stats and season summary
• get_team_h2h — Head-to-head record between two franchises
• get_venue_hub — Aggregated venue patterns: par scores, toss impact, phase splits
• get_standings — IPL 2026 points table with NRR
• get_trend — A single trend insight with full claim set
• list_trends — Browse trends by category (conditional, momentum, venue, toss, anomaly)

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. CricketStudio MCP's toolset — get_dataset_summary, search_players, get_player_profile and 11 more — is a fair guide to whether it matches your workflow. It is maintained by i-m-arul; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch CricketStudio MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cricketstudio mcp mcp server does with a few real requests.