searchLABSCO SUMMARY
Hockey records without the HTML in the way.
Lookups return structured records — leagues, teams, rosters, player and staff profiles — so a question about a prospect's season is answered from data rather than from a page an assistant has to interpret. Players and staff are separate id spaces, and each profile points at the other when someone holds both.
What it is
Unofficial access to eliteprospects.com hockey data — leagues, teams, players and staff — as structured output rather than scraped HTML. One TypeScript core backs two front ends: a command-line tool, and an MCP server exposing the same lookups to clients such as Claude.
What you get
- Every league listed, filterable by a 2- or 3-letter country code (list_leagues)
- A single league with its metadata, teams and available seasons, optionally for one season (get_league)
- A team by id, with metadata, roster and available seasons (get_team)
- A player's profile by id: bio, draft and current team (get_player)
- A staff member's profile by id, with role and current team (get_staff)
- Player and staff kept in separate id namespaces, with each profile linking to the same person's other one
- No API key, and nothing to compile — Bun runs the TypeScript straight from the clone
Requirements
Bun, which runs the TypeScript directly. No API key.
Setup effort
Build from source
USE CASES
01
Checking a prospect's season
A player's profile comes back by id with bio, draft details and current team, so the answer is the record rather than a summary of one.
02
Reading a full roster
A team by id returns its metadata, roster and the seasons available, and the league view gives the surrounding context.
03
Finding the leagues in a country
The league list filters by a two- or three-letter country code, which is the fastest way into an unfamiliar hockey nation.
04
Checking who is behind the bench
Staff profiles are their own lookup with role and current team, since a staff id and a player id can point at different people.
6 tools
Listed in project docs. Your client may show a different list.
list_leaguesget_leagueget_teamget_playerget_staffBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/troelskn/eliteprospectsMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"eliteprospects": {
"command": "bun",
"args": [
"<YOUR_PATH_TO_ELITEPROSPECTS>/bin/eliteprospects-mcp"
]
}
}
}
