College football data is field-heavy, and a model guessing at column names produces plausible nonsense. Here the schema for each endpoint is available as a resource, so a question like which drives ended in a turnover inside the twenty gets translated against real field definitions. The prompt templates cover the analyses people ask for repeatedly — one game, one team, a season trend, a head-to-head, a rivalry — and the honest constraint is the rate limit rather than the data.
A Python server over the College Football Data API V2 that exposes the game, team, play and ranking endpoints, with schema documentation attached so a model knows what each field means.
- get-games and get-games-teams — results, scores and per-team game statistics
- get-records — team season records
- get-plays and get-play-stats — play-by-play data and individual play statistics
- get-drives — drive summaries and how they ended
- get-rankings — team rankings across the polls
- get-pregame-win-probability and get-advanced-box-score — win probability and advanced box score analytics
- Schema documentation for every endpoint as resources, so the model reads the field definitions before querying
- Prompt templates for common analyses: analyze-game, analyze-team, analyze-trends, compare-teams and analyze-rivalry
A College Football Data API key in CFB_API_KEY — free to obtain. Python 3.11 or higher with uv. The free tier is rate limited; Patreon subscribers get higher limits, so wide season-long queries need to be spaced out.
One command plus a key — npx -y @smithery/cli install cfbd --client claude, then supply credentials