
Connects Claude to live NHL data through the official NHL API via the Pipeworx gateway. The source doesn't list specific tools, but this is part of Pipeworx's collection of 673+ data sources, so you're likely getting access to scores, schedules, team stats, and player information. You can either call tools directly or use the ask_pipeworx wrapper to query in plain English and let it route to the right endpoint. Useful when you're building hockey analytics, need current game data in your workflow, or want to answer NHL questions without leaving your AI client. Runs over streamable HTTP, so no local setup required.
NHL MCP — live NHL data via the official NHL API
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_standings | Check current NHL standings. Returns wins, losses, OT losses, points, goals for/against, and streak info for all teams. |
get_scores | Get today's NHL game scores and status (live, final, or scheduled). Returns teams, scores, shots on goal, and current period. |
get_schedule | Get the current NHL weekly schedule. Returns upcoming and recent games with teams, dates, times, and venues. |
get_player | Get an NHL player's profile and current season stats by player ID. Returns bio, position, team, and season statistics. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"nhl": {
"url": "https://gateway.pipeworx.io/nhl/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/nhl/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Nhl data" })
The gateway picks the right tool and fills the arguments automatically.
MIT