Mcp_mlb_statsapi

Created By
mpizzaa year ago
This project provides an MCP (Multi-Channel Pipeline) server that acts as a wrapper for the MLB Stats API. It allows you to easily access and process various MLB data points, including schedules, game results, and team information. This server is designed for efficient data retrieval and processing within an MCP framework.
Overview

what is baseball-mcp?

baseball-mcp is an MLB Stats API wrapper that provides an MCP (Multi-Channel Pipeline) server for easy access to various MLB data points, including schedules, game results, and team information.

how to use baseball-mcp?

To use baseball-mcp, install the package via PyPI using pip install mcp_mlb_statsapi, or clone the repository and run it from the source code. You can interact with the server using the MCP client.

key features of baseball-mcp?

  • Retrieve MLB game schedules for specified date ranges.
  • Fetch daily game results, including scores and winning teams.
  • Get detailed results for a specific team's most recent game.
  • Look up player IDs using names with fuzzy matching support.

use cases of baseball-mcp?

  1. Accessing real-time MLB game schedules and results.
  2. Analyzing team performance over a season.
  3. Integrating MLB data into sports applications or websites.

FAQ from baseball-mcp?

  • Is baseball-mcp free to use?

Yes! baseball-mcp is licensed under the MIT License, allowing free use and modification.

  • How can I contribute to baseball-mcp?

Contributions are welcome! You can open an issue or submit a pull request on the GitHub repository.

  • What programming language is baseball-mcp written in?

baseball-mcp is written in Python.

Server Config

{
  "mcpServers": {
    "mcp_mlb_statsapi": {
      "command": "{YOUR_PYTHON_EXECUTABLE_PATH}/python",
      "args": [
        "-m",
        "mcp_mlb_statsapi"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mpizza
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago