Can an AI agent like Claude manage my hockey league?

Yes. Hockey Line Leagues exposes its league-operations tools to external AI agents over MCP (Model Context Protocol), a REST API, and a CLI. Connect Claude or any MCP-compatible agent with an org API key and it can create leagues and seasons, add teams and rosters, generate round-robin schedules, record scores, and read standings.

Is it safe to give an AI agent access to my league?

Keys are scoped to a single rink and revocable instantly. A scorekeeper-role key can only read data and record scores, so it cannot change your league structure. Write operations follow the same subscription rules as the dashboard, and every change an agent makes is visible in your dashboard.

Is there an API for hockey league management?

Yes. Hockey Line Leagues has a REST API with a self-describing tool catalog (hockeylineapp.com/api/v1/tools), an OpenAPI 3.1 spec, a remote MCP endpoint for AI agents, and a zero-dependency CLI (npx hockey-line-cli). All three expose the same league operations: seasons, teams, rosters, schedules, scores, and standings.

Run Your Hockey League with an AI Agent (Claude + MCP)

Q: How do I connect Claude to Hockey Line Leagues?

Create an API key in your rink dashboard under Settings → API & Agents, then add the remote MCP server: claude mcp add --transport http hockey-line https://hockeylineapp.com/api/mcp --header "Authorization: Bearer rk_your_key". Claude Desktop, Cursor, and other MCP clients connect with the same URL and header in their MCP config.

Rink admins have been asking for this one since the day our in-app AI assistant shipped: "Can I just have my own AI do this?" As of now, yes. Hockey Line Leagues is agent-native — Claude, Cursor, or any AI agent you already use can run your league for you: build seasons, manage rosters, generate schedules, record scores, and pull standings.

This guide shows you how to hand your league to your agent in about five minutes, and what it can do once it's in.

What "agent-native" actually means

Everything our built-in setup assistant can do is exposed to your tools through three doors, all speaking the same language:

An MCP endpoint — the Model Context Protocol server at hockeylineapp.com/api/mcp. Point Claude (or any MCP client) at it and your agent gets 17 league-operations tools.
A REST API — clean JSON endpoints with a self-describing tool catalog and an OpenAPI spec, for scripts and custom integrations.
A CLI — npx hockey-line-cli, JSON in and JSON out, perfect for terminal agents and cron jobs.

One implementation under the hood, so a schedule your agent generates over MCP looks exactly like one built in the dashboard — same round-robin engine, same timezone handling, same mobile-app sync.

Step 1: Create an API key

In your rink dashboard, open Settings → API & Agents and create a key. Two roles are available:

Admin — full league operations: leagues, seasons, teams, rosters, schedules, scores.
Scorekeeper — read everything, record scores. Perfect for a game-night agent that should never touch your league structure.

The key is shown once — copy it somewhere safe. You can revoke any key instantly, and every key is scoped to your rink only.

Step 2: Connect your agent

For Claude Code, it's one command:

claude mcp add --transport http hockey-line https://hockeylineapp.com/api/mcp \
  --header "Authorization: Bearer rk_your_key"

For Claude Desktop, Cursor, or any other MCP client, add this to your MCP config:

{
  "mcpServers": {
    "hockey-line": {
      "url": "https://hockeylineapp.com/api/mcp",
      "headers": { "Authorization": "Bearer rk_your_key" }
    }
  }
}

That's the whole integration. No SDK, no webhook wiring.

Step 3: Talk to it like a league manager

Your agent discovers your leagues, seasons, and teams on its own — you just say what you want:

"Set up the Winter season: same teams as fall, weekly games on Sundays at 8:00 and 9:15pm, starting January 10."

The agent creates the season with returning teams carried over (identities, divisions, and app links intact), generates a balanced round-robin schedule in your rink's timezone, and reports back. Other things rinks are doing:

Game night: "Record tonight's scores: Ice Holes 4, Puck Hogs 2 in OT. Zambonis 3, Cold Fronts 1." — standings, playoff series, and the mobile app update instantly.
Mid-season admin: "Move Friday's late game to Sunday at 7pm and mark the 9:30 game postponed."
Roster churn: "Add these six players to the Cold Fronts from this email…" — paste and go.
Reporting: "Give me the standings and top scorers, formatted for our newsletter."

The guardrails (because it's your league)

Keys are scoped and revocable. One rink per key, kill it anytime in the dashboard.
Roles limit blast radius. A scorekeeper key physically cannot restructure your league.
Reads are always free; writes follow your plan. The same subscription rules as the dashboard apply to agents.
Nothing is hidden. Every change lands in the same dashboard you already use, so you can review what your agent did.

For the technically curious

The full tool catalog (with JSON Schemas) is public at /api/v1/tools, there's an OpenAPI 3.1 spec, and the developer & agent docs cover everything — including example prompts and the CLI. If you're building something custom, the REST door works everywhere:

curl -X POST https://hockeylineapp.com/api/v1/tools/get_standings \
  -H "Authorization: Bearer rk_your_key" \
  -d '{"seasonId": "..."}'

Why we built this

League management is coordination work, and coordination work is exactly what AI agents are getting good at. You shouldn't have to choose between "modern platform" and "works with my tools." Pointstreak never gave you an export button; we'd rather give you the whole API.

Create your rink, grab an API key from Settings → API & Agents, and let your agent take the next roster paste, the next schedule build, and the next scores night off your plate. See it from the player side first on the demo rink.

Run Your Hockey League with an AI Agent (Claude, MCP & the Agent API)