{
  "markdown": "# mcp-cricket\n\nCricket MCP — wraps CricAPI (api.cricapi.com) for live cricket data.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `current_matches` | List current and recent cricket matches (Test/ODI/T20) with live scores, teams, venue, and status. Use this for \"what cricket matches are live/on right now\". Returns match IDs usable with match_info. |\n| `match_scores` | Get a lightweight feed of live cricket scores across current matches. Returns each match as a compact \"team1 vs team2\" with running scores and status. Best for quick live cricket score checks. |\n| `search_players` | Search for cricket players by name. Returns player IDs, names, and country. Use this to look up a cricketer before fetching more detail. |\n| `match_info` | Get full information and scorecard for a single cricket match (Test/ODI/T20) by its match ID. Returns teams, venue, innings scores, toss, and winner. Get the id from current_matches. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"cricket\": {\n      \"url\": \"https://gateway.pipeworx.io/cricket/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/cricket/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Cricket data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3077,
  "sha": "c62034c8f3d67b039f45d3af59ab6ffdac75fd6eb94784fca1f7b36bc66940dc",
  "repo_slug": "pipeworx-io/mcp-cricket",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_cricket_3efd720d/readme"
}