TeamCalendar
Language

Documentation

TeamCalendar for AI agents

TeamCalendar runs an MCP (Model Context Protocol) server. An AI assistant connected to it can answer what games are on today, read a team's schedule and a league's standings, and make a calendar for you to subscribe to.

The server

  • Address: https://teamcalendar.com/api/mcp
  • Transport: Streamable HTTP
  • Sign-in: None. Reading schedules and making a calendar need no account, key or token.

The admin tools are for TeamCalendar's own operators, who connect with a personal access token. Nobody else needs one.

Example: today's games

Call get_leagues for the leagues TeamCalendar follows, then get_league_slate with days: 1 for each league you want.

get_leagues {}
get_league_slate {"code": "NFL", "days": 1}
get_league_slate {"code": "NBA", "days": 1}

"Today" is the league's own day, in its time zone, not the caller's. Pass days: 7 for the week ahead, or a team id to narrow the slate to one club.

Example: make a calendar

Find the team with find_teams, then call create_composed_calendar with the teams chosen, or create_named_calendar with a name such as "broncos". The answer holds a feedUrl and a returnUrl, both paths on https://teamcalendar.com.

Subscribe to the feed in Google Calendar, Apple Calendar or Outlook. Open the return address to change the teams later.

Connecting an assistant

In Claude, ChatGPT or another assistant that takes a remote MCP server, add the address above as a custom connector and choose no authentication. A client set up from a file takes:

{
  "mcpServers": {
    "teamcalendar": {"type": "http", "url": "https://teamcalendar.com/api/mcp"}
  }
}

Discovery

A client that discovers servers by domain reads the AI Catalog, which names the Server Card. A plain-text summary for agents is in llms.txt.

More Articles