ipl-schedule-api-mcp-server

Created By
shabbirdwd53a year ago
ipl-schedule-api-mcp-server
Overview

what is ipl-schedule-api-mcp-server?

ipl-schedule-api-mcp-server is an API server designed to provide schedules and information related to the Indian Premier League (IPL) cricket matches.

how to use ipl-schedule-api-mcp-server?

To use the API, developers can send HTTP requests to the server endpoints to retrieve match schedules, team information, and other related data.

key features of ipl-schedule-api-mcp-server?

  • Provides real-time IPL match schedules
  • Access to team and player statistics
  • Easy integration with web and mobile applications

use cases of ipl-schedule-api-mcp-server?

  1. Building sports applications that display live match schedules.
  2. Integrating IPL data into fantasy cricket platforms.
  3. Creating dashboards for sports analytics.

FAQ from ipl-schedule-api-mcp-server?

  • What data can I retrieve from the API?

You can retrieve match schedules, team details, and player statistics.

  • Is there a limit on API requests?

Yes, please refer to the API documentation for rate limits.

  • How do I get started with the API?

You can get started by visiting the GitHub repository and following the setup instructions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shabbirdwd53
Star
0
Language
Java
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)

3 hours ago
Myrsu
@VidhiJav

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago