Cricketstudio Mcp

What is Cricketstudio MCP?

Cricketstudio MCP is a Model Context Protocol (MCP) server that gives any MCP-compatible AI client — such as Claude Desktop, Cursor, or ChatGPT Connectors — structured, citable access to cricket data. Every response includes a canonicalUrl back to players.cricketstudio.ai, an explicit date window, a sample-size count, and a provenance trail. The data is fully bundled in the package, so all 32 tools run locally with zero network calls, no API keys, and no rate limits.

How to use Cricketstudio MCP?

Add a configuration entry to your MCP client (e.g., Claude Desktop's claude_desktop_config.json) with the command npx cricketstudio-mcp. The server starts on stdin/stdout and requires Node 20 or later. For other MCP clients, run npx cricketstudio-mcp directly.

Key features of Cricketstudio MCP

• 32 tools including a knowledge-graph layer
• Zero network calls – data bundled in the package
• No API keys or rate limits
• Sample-size floors: ≥30 balls for batting, ≥15 for bowling
• Every response includes canonicalUrl, dataAsOf, and sampleSize
• Supports IPL 2026, full IPL history, and MLC 2023–2026

Use cases of Cricketstudio MCP

• Query IPL 2026 match summaries, player stats, and standings
• Compare two or more players side-by-side
• Explore head-to-head records between batters and bowlers
• Retrieve all-time IPL leaderboards for runs, wickets, sixes, etc.
• Analyze MLC matches and player profiles

FAQ from Cricketstudio MCP

What data is included in Cricketstudio MCP?

The bundled snapshot covers IPL 2026 (complete season, RCB champions), 18 seasons of IPL history (2007/08–2025, Cricsheet), and Major League Cricket 2023–2026 (Cricsheet) — 1,317 matches and 312,309 deliveries total. The data is released under CC BY 4.0.

How are sample-size floors enforced?

Batting claims require at least 30 balls faced; bowling claims require 15 deliveries. Venue claims need ≥3 fixtures; trend claims need ≥3 matches. Claims below these thresholds are simply absent from the responses.

Does Cricketstudio MCP require an internet connection or API key?

No. The data is fully bundled locally; no network calls are made for tool responses. One anonymous startup ping is sent for usage counting, which can be disabled with CRICKETSTUDIO_NO_TELEMETRY=1.

How is the data licensed?

The code is MIT licensed; the bundled data is CC BY 4.0. Attribution flows automatically via the canonicalUrl field in every tool response, pointing to CricketStudio.

What is the update cadence?

The bundled snapshot is refreshed after each CricketStudio data update. Every tool response includes dataAsOf so freshness can be explicitly disclosed.