Cricket Mcp Server

Created By
tarun7ra year ago
A MCP server for fetching cricket data from Cricbuzz, including player statistics, live match scores, upcoming schedules, and the latest news.
Overview

What is Cricket MCP Server?

Cricket MCP Server is a Model Context Protocol (MCP) server that provides comprehensive cricket data from Cricbuzz, including player statistics, live match scores, upcoming schedules, and the latest news.

How to use Cricket MCP Server?

To use the Cricket MCP Server, clone the repository, install the required dependencies, and run the server using the provided commands. You can also interact with it through a Gradio web interface.

Key features of Cricket MCP Server?

  • Player Statistics: Access detailed cricket player stats across all formats (Test, ODI, T20).
  • Live Matches: Fetch currently ongoing cricket matches.
  • Match Schedule: Get upcoming cricket match schedules.
  • Cricket News: Stay updated with the latest cricket news and updates.

Use cases of Cricket MCP Server?

  1. Fetching real-time player statistics for analysis.
  2. Monitoring live cricket matches and scores.
  3. Keeping track of upcoming cricket match schedules.
  4. Accessing the latest news articles related to cricket.

FAQ from Cricket MCP Server?

  • Can I get statistics for any cricket player?

Yes! You can fetch statistics for any player by providing their name.

  • Is there a web interface available?

Yes! You can interact with the server using a Gradio web UI.

  • How do I install the server?

Clone the repository and run pip install -r requirements.txt to install the dependencies.

Server Config

{
  "mcpServers": {
    "cricket": {
      "command": "python",
      "args": [
        "cricket_server.py"
      ],
      "cwd": "/path/to/cricket-mcp-server"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tarun7r
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago