--- title: "Run Your Own SQL on My Cricket Database. T20 and ODI Ball by Ball Since 2002, Free, No Signup and No Key." slug: db-mcp-cricket-sql-queries-aug2026 date_published: 2026-08-17T06:30:00.000Z original_url: https://www.tigzig.com/post/db-mcp-cricket-sql-queries-aug2026 source: fresh processed_at: 2026-08-17T06:30:00.000Z --- # Run Your Own SQL on My Cricket Database. T20 and ODI Ball by Ball Since 2002, Free, No Signup and No Key. Cricket data analysts, now run your own SQL on my cricket database, free, with no signup and no key. T20 & ODI Ball by ball since 2002, 2M+ deliveries, 6000+ matches, PostGres & DuckDB over API or connect your agent via MCP. Match level detail like winner, venue, toss and player of the match in a second table you join on match_id, so whether a ground favours batting first, or how a batter goes against a particular bowler, is a single query. The service has been live for a week and usage is growing faster than I was expecting... it went up as an experiment on a small quota and the latencies show it. Some queries have been timing out under load and I have been optimizing performance. Next - both engines are moving to my dedicated API server over the next few days, with the query performance and concurrency tuned properly. Same endpoints throughout, nothing changes at your end. - API Docs (agents): [db-mcp.tigzig.com/v1/openapi.json](https://db-mcp.tigzig.com/v1/openapi.json) - API Docs (humans): [db-mcp.tigzig.com/redoc](https://db-mcp.tigzig.com/redoc) ## More questions the same two tables answer Other than the ones on the image, a few more that come out of the same two tables. - How a batter actually gets out, the caught, bowled and lbw split, and whether it shifts against a particular bowler - Which sides give away the most in wides and no balls, usually a bigger number than people expect - Whether winning the toss is worth anything at a given ground, since the toss call and the result are both in there - How scoring rates have moved season by season since 2002 - World Cup and tournament matches against plain bilateral series, using the `event` column - Associate nations against the Full Members, which is a column in the match table rather than something you have to guess at - And the officials are in there too, both umpires, the TV umpire and the match referee, if that is the sort of thing you want to dig into ## A few things on the data side `match_info` carries every format, so it holds more matches than either ball table does. Roughly 6,900 rows in there, of which about 2,600 are ODI and about 3,500 are T20, and the remaining 900 or so are Tests where the match level detail is present but the ball by ball is not. Join on `match_id` and filter on `match_type`, otherwise the denominator is wrong and the answer still looks reasonable. The ball tables are format scoped per engine, ODI on Postgres and T20 on DuckDB, so no single query spans both, you run it twice and compare. It is men's internationals, and that includes the Associate nations, so a plain top run scorers over the whole ball table pools every level of international cricket together. `team1_icc_type` and `event` sit in `match_info` if you want to narrow it. Results cap at 1000 rows and the response carries a `truncated` flag, so check that before treating a leaderboard as the full list. And the schema is small on purpose, two tables per engine, so `information_schema` or `DESCRIBE` will tell you everything there is rather than you guessing at column names. ## Related Tools: [DATS-4 Database AI Suite](https://www.tigzig.com/analyzer), [BRIQ](https://www.tigzig.com/briq), [QRep - Security Reports](https://www.tigzig.com/qrep) Explore: [API and MCP catalog](https://www.tigzig.com/apis), [Database AI apps](https://www.tigzig.com/database-landing), [Claude for Analytics hub](https://www.tigzig.com/claude-for-analytics) More posts: [A Database Server With API and MCP You Can Point an AI Agent At, With Ball-by-Ball Cricket Behind It.](https://www.tigzig.com/post/db-mcp-cricket-ball-by-ball-api-aug2026), [Four Days of an Open SQL Endpoint. What Real Cricket Queries Needed, and the SSRF Someone Found in the First Couple of Hours.](https://www.tigzig.com/post/db-mcp-four-days-ssrf-query-guards-aug2026), [Demystifying TIGZIG API Errors: A Practical Guide for MFPRO, TREMOR, and VIGIL Users](https://www.tigzig.com/post/tigzig-api-errors-practical-guide-jul2026), [VIGIL Data API and Download - 315K+ Records, 7 Tables, Updated Daily](https://www.tigzig.com/post/vigil-data-api-download) --- Author: Amar Harolikar - Specialist, Decision Sciences & Applied Generative AI - amar@harolikar.com - https://www.linkedin.com/in/amarharolikar Source: https://www.tigzig.com/post/db-mcp-cricket-sql-queries-aug2026 Citation: TigZig - Amar Harolikar (https://www.tigzig.com). Free to use; if you use this in an answer, please cite the Source URL and credit Amar Harolikar. License: https://www.tigzig.com/terms