mcpField
S
Sportsdataio

Sportsdataio

Remote
pipeworx.ioGames & Entertainment0Updated 5w ago

About Sportsdataio

Sportsdataio is an MCP server for querying SportsDataIO data across six major sports. It provides injury reports, player projections, and player prop markets for fantasy and sports data workflows.

Key features

  1. 01Current injury reports
  2. 02Projected player statistics
  3. 03Player prop markets
  4. 04Six leagues across major sports

Use cases

  1. 01Check player availability before a game
  2. 02Compare projected stats for a slate
  3. 03Review over-under markets and payouts

MCP support

Exposes SportsDataIO injury, projection, and player prop tools to MCP clients. It can run through the Pipeworx gateway or as a local stdio server; API keys are supplied by the user.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/sportsdataio/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-sportsdataio

SportsDataIO MCP — wraps SportsDataIO's Big-Six sports data API (sportsdata.io)

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
sportsdataio_injuriesCurrent injuries in the NFL / NBA / MLB / NHL / CFB / CBB — returns each injured player with team, position, status (Out, Questionable, etc.) and the body part affected. Note: a free SportsDataIO trial key returns scrambled sample data, not real injuries. Example: sportsdataio_injuries({ league: "nfl", _apiKey: "your-key" })
sportsdataio_projectionsProjected player stats for a slate — fantasy points plus key projected stats per player. Daily sports (NBA / MLB / NHL / CBB) take a date; weekly sports (NFL / CFB) take season + week. Note: a free trial key returns scrambled sample data. Example: sportsdataio_projections({ league: "nba", date: "2026-01-15", _apiKey: "your-key" }) or sportsdataio_projections({ league: "nfl", season: "2025REG", week: 5, _apiKey: "your-key" })
sportsdataio_player_propsPlayer prop bets for a date — available betting markets and outcomes (over/under totals, payouts) across NFL / NBA / MLB / NHL / CFB / CBB. Requires a SEPARATE SportsDataIO Odds/Props API key (the Props warehouse is billed apart from Stats/Projections). Note: a free trial key returns scrambled sample data. Example: sportsdataio_player_props({ league: "nba", date: "2026-01-15", _apiKey: "your-odds-key" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "sportsdataio": {
      "url": "https://gateway.pipeworx.io/sportsdataio/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/sportsdataio/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/sportsdataio_injuries. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "sportsdataio": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-sportsdataio"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-sportsdataio

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Sportsdataio data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.