Thesportsdb MCP server

@pipeworx/thesportsdb

TheSportsDB MCP — sports catalog across 50+ leagues: teams, players, events, venues, league tables. Free tier with public key.

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

Tools

• listsports() / listleagues(sport?, country?)
• searchteams(query), getteam(teamid), leagueteams(league_id)
• searchplayers(query) / getplayer(player_id)
• teameventslast(teamid) / teameventsnext(teamid)
• eventsbyday(date, sport?, league?)
• leaguetable(leagueid, season?)

Auth

The free public tier uses API key 3 (well-known, no signup required). Pipeworx defaults to this. For higher rate limits / extra endpoints register at https://www.thesportsdb.com/ and BYO via ?_apiKey=.

Data source

https://www.thesportsdb.com/api/v1/json//

Match detail (eventdetail, eventtimeline, eventstats, eventlineup)

Four per-match tools for settling questions about a single fixture: the scoreline and venue (eventdetail), goals with scorer/assist/minute plus cards and substitutions (eventtimeline), team-by-team statistics (eventstats), and the starting eleven plus substitutes (eventlineup). All take a TheSportsDB eventid — find one with eventsbyday, teameventslast or teamevents_next.

They are NOT premium-gated — but the free tier truncates them

Measured 2026-09-12 on the free public key: all four endpoints return real data, so no key is required and none of these tools refuses for want of one.

What the free tier does do is cap each array at 5 rows, silently. On idEvent 2594568 (Bayern Munich vs Bodø/Glimt, final score 5-0) the timeline returns 5 rows, the earliest at minute 45, containing 2 goals — every first-half goal is absent. eventstats returns 5 statistics and does not include shots on goal, corners or possession. eventlineup returns 5 players. intHomeScoreHT / intAwayScoreHT come back null.

So for a settlement workload a supporter key matters — for completeness, not for access. Pass it as _apiKey.

How the tools tell you

eventtimeline cross-checks the goals it can see against the event's own final score. When they disagree it returns complete: false with goalsintimeline, goalsinfinalscore and a note saying not to settle a first-scorer or half-time question from it. That is proof of truncation, not a guess. eventstats and eventlineup have no equivalent invariant, so they report complete: null when exactly 5 rows come back — which may be a whole small result or a truncated large one, and from the response alone those are indistinguishable.

Coverage is per-competition

A match the source has not covered returns found: false with a reason, never an error and never a wrong answer. The tools distinguish two cases that arrive identically from upstream (both are a bare null): notimelineforevent — the match exists and is named back to you, the source just has no timeline for that competition — versus nodataandevent_unconfirmed, where the event id could not be confirmed either. For a caller settling a market those are opposite conclusions: "ask a different source" versus "you have the wrong match".

Quick Start

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

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

What this endpoint actually serves

Shortened. The full README is on GitHub.