Espn
ESPN MCP — keyless multi-sport live scores, teams, and news via ESPN's public site API.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http espn 'https://gateway.pipeworx.io/espn/mcp'{
"mcpServers": {
"espn": {
"type": "http",
"url": "https://gateway.pipeworx.io/espn/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
mcp-espn
ESPN MCP — keyless multi-sport live scores, teams, and news via ESPN's public site API.
Part of Pipeworx — an MCP gateway connecting AI agents to 1866+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
get_scoreboard | Live sports scores: NFL/NBA/MLB/NHL/soccer/college scores for today's games and results. Returns each game with teams, scores, status (live/final), clock, and period. |
get_teams | List all teams (rosters/franchises) for a league: names, abbreviations, locations, and colors. Works for NFL/NBA/MLB/NHL/soccer/college. |
get_news | Latest sports news headlines for a league: NFL/NBA/MLB/NHL/soccer/college articles with summaries and links. |
get_standings | League standings / table: win-loss records, win %, games behind (and points/draws for soccer), grouped by conference/division. PREFER for "NBA standings", "Premier League table", "NFL division standings", "who is leading <league>". |
get_team_schedule | A team's schedule — upcoming and recent games with dates, opponents, and (for finished games) scores and result. PREFER for "when do the Lakers play next", "<team>'s schedule", "<team> recent results". Get the numeric team_id from get_teams. |
get_game_summary | A completed or in-progress game's box score: per-player stats by team (e.g. goals/assists/shots for hockey, passing/rushing for football), scoring plays in order, and game leaders (top performer per stat category). PREFER for "box score for <game>", "<team> vs <team> player stats", "who scored in <game>". Get the numeric event_id from get_scoreboard or get_team_schedule. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"espn": {
"url": "https://gateway.pipeworx.io/espn/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/espn/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 1866+ 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
curl -X POST https://gateway.pipeworx.io/v1/tools/get_scoreboard \
-H 'Content-Type: application/json' \
-d '{"sport":"football","league":"nfl"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/get_scoreboard. 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": {
"espn": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-espn"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-espnIt 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 Espn data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Questions fréquentes
Qu'est-ce que Espn ?
ESPN MCP — keyless multi-sport live scores, teams, and news via ESPN's public site API.
Comment installer Espn ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http espn 'https://gateway.pipeworx.io/espn/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Espn ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Espn est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Espn ?
Il est publié par pipeworx-io. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.