Jweingardt12 Mlb Mcp
Pull MLB, Statcast, Savant, and FanGraphs stats into agent workflows while building sports dashboards, research bots, or content pipelines.
Overview
ai.smithery/jweingardt12-mlb_mcp is a Build-phase MCP server that lets agents query MLB, Savant, Statcast, and FanGraphs baseball data through Smithery.
What is this MCP server?
- Unified access to MLB official data, Baseball Savant, Statcast, and Fangraphs from one MCP remote
- Streamable-HTTP Smithery endpoint with Bearer smithery_api_key authentication
- Suited for detailed stat queries agents can compose into apps, newsletters, or research notebooks
- Catalog version 1.16.0 on MCP server schema 2025-09-16
- Remote-first: no local install described beyond registering the Smithery URL in your agent
- Server schema dated 2025-09-16; catalog version 1.16.0
- One streamable-HTTP remote on server.smithery.ai
- Documents four baseball data families: MLB, Baseball Savant, Statcast, and Fangraphs
What problem does it solve?
Agents guess player and pitch-level stats because pulling Savant, Statcast, and FanGraphs manually breaks flow and invites errors.
Who is it for?
Indie builders prototyping sports analytics APIs, automated recap drafts, or scouting notebooks that must cite real Statcast and FanGraphs fields.
Skip if: Teams with no baseball use case, or anyone who needs a turnkey fantasy app without writing integration and compliance logic themselves.
What do I get? / Deliverables
After you register the Smithery remote, your agent can request authoritative baseball metrics inside the same session where you code or draft content.
- Registered Smithery remote pointing at @jweingardt12/mlb_mcp
- Agent-callable queries across MLB, Savant, Statcast, and FanGraphs-shaped tool responses
- Reusable stat-fetch patterns for apps, reports, or research workflows you implement next
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server exists to wire external baseball data sources into products and automations, not to run a whole go-to-market phase on its own. Integrations is the right subphase: it exposes remote MCP tools over Smithery streamable HTTP rather than replacing frontend, backend, or docs work.
How it compares
MCP data bridge to four baseball sources, not a hosted fantasy league or a generic web-scraping skill.
Common Questions / FAQ
Who is ai.smithery/jweingardt12-mlb_mcp for?
Solo builders and small teams building agent-assisted sports analytics, content, or research tools that depend on MLB and advanced metrics feeds.
When should I use ai.smithery/jweingardt12-mlb_mcp?
Use it during Build when you are integrating live baseball statistics into an app, script, or editorial workflow instead of copying stats by hand.
How do I add ai.smithery/jweingardt12-mlb_mcp to my agent?
Add the Smithery streamable-HTTP remote URL for @jweingardt12/mlb_mcp and set Authorization to Bearer followed by your smithery_api_key in your MCP client config.