home / mcp / nhl go mcp server

NHL Go MCP Server

Exposes NHL API data via MCP for easy integration with LLMs and MCP clients.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "carsonjones-nhl-go": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/inspector",
        "./nhl-mcp"
      ]
    }
  }
}

You can access NHL data through a Model Context Protocol (MCP) server implemented in Go. This server exposes API data and makes it easy to integrate NHL data into large language model workflows and other MCP-enabled clients.

How to use

Use the MCP server by running it as a local stdio MCP process and connecting your MCP client (such as a model workflow or inspector tool) to it. The server focuses on NHL API data access via MCP, enabling you to query teams, players, schedules, and standings and have them surfaced in your conversations, tools, and automations.

How to install

Prerequisites you need on your machine before starting:

Install steps

# Prerequisites
# - Go toolchain (version >= 1.23 is recommended for local development)
# - Git

# 1) Build the NHL MCP server binary
cd ./mcp
go build -o nhl-mcp

# 2) (Optional) Build main NHL binaries if you also work with the CLI/API client
# from the project root
cd ..
go build -o nhl

# 3) Start or test the MCP binary with an inspector (for debugging)
# This runs the MCP server via the inspector tool to expose MCP endpoints locally
npx @modelcontextprotocol/inspector ./nhl-mcp

# 4) If you want the MCP path to be used by a desktop client, configure:
# In your claude_desktop_config.json, add the path to the nhl-mcp executable
# Example:
# "nhl": {
#   "command": "/path/to/nhl-mcp"
# }

Configure your MCP client

Create or update your MCP client configuration to point to the local inspector command for the NHL MCP server. The example below shows how to invoke the MCP server via the inspector so your client can query NHL data through the MCP endpoints.

Notes

A complete local development flow can include cloning the repository, building both the NHL CLI and the nhl-mcp server, and verifying the MCP server with the inspector tool. If you plan to integrate with a desktop launcher or assistant, ensure the nhl-mcp binary path is correctly referenced in your MCP client config.

Configuration examples

{
  "mcpServers": {
    "nhl_mcp": {
      "type": "stdio",
      "name": "nhl_mcp",
      "command": "npx",
      "args": ["@modelcontextprotocol/inspector","./nhl-mcp"]
    }
  }
}

Troubleshooting

If the inspector cannot connect to the NHL MCP server, verify that the nhl-mcp binary is built and accessible at the specified path. Ensure you have node and npm/npx available for the inspector command. Confirm the nhl-mcp executable has execute permissions on your system.

Available tools

API Client

A Go-based wrapper around the NHL API enabling access to teams, players stats, schedules, and standings.

CLI

Command-line interface to query NHL data and interact with the NHL API client.

MCP Server

A Model Context Protocol server that exposes NHL API data for MCP-enabled clients and workflows.