openfoot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENFOOT_API_KEY | Yes | Your OpenFootAPI key. Get one at https://openfootapi.com/pricing. Required for most tools, though openfoot_health works without it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| openfoot_competitionsA | List the competitions OpenFootAPI supports, with IDs, country codes, tiers and provider coverage. Use this first when you need a valid competition ID. |
| openfoot_searchA | Search for teams or competitions by fuzzy name to find their canonical OpenFootAPI IDs. |
| openfoot_matchesA | List fixtures and results with scores, kickoff times, status and teams. Filter by competition, team, status, date or season. |
| openfoot_standingsA | Get the league table for a competition — rank, points, played, won, drawn, lost, goals for/against, goal difference and recent form. |
| openfoot_match_lineupsA | Confirmed starting XI, benches and formations for a match. |
| openfoot_match_eventsA | Timeline of events in a match: goals, assists, yellow/red cards, substitutions, VAR checks, plus live minute-by-minute text commentary. |
| openfoot_match_xgA | Shot-level Expected Goals data with coordinates on the pitch, shot type, situation (open play, penalty, corner), outcome and cumulative xG. |
| openfoot_match_contextA | A complete pre-match or post-match dossier assembled for analysis: recent form, Elo delta, rest days, head-to-head record and model-derived fair match probabilities. |
| openfoot_league_xgA | Season-level Expected Goals analytics for a league — teams ranked by xG generated, xG conceded, over/underperformance vs real goals, and shot efficiency. |
| openfoot_oddsB | Fair 1X2 and over/under 2.5 probabilities derived from underlying team form, Elo delta and xG performance. |
| openfoot_quotaA | Check your API key's tier, monthly request allowance, requests used this month and reset date. |
| openfoot_healthA | Check the operational status of OpenFootAPI without authentication. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| scout_team_form | Build a dossier on a team: recent results, xG trend, upcoming fixtures and key strengths. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct data domain, from standings and lineups to events and xG. Minor overlap exists between match_context and odds since both derive probabilities, but the descriptions clarify that context is a broader dossier while odds is dedicated betting-market output.
All tools follow a consistent openfoot_ prefix followed by a clear resource or action name, using snake_case throughout. Whether a tool describes matches, standings, or quota, the naming pattern is predictable and unambiguous.
Twelve tools is a well-scoped number for a football data API. Each tool represents a meaningful data product, including meta tools like quota and health, with no redundant or filler endpoints.
The surface covers the core football data workflow: identifying competitions, searching teams, fetching matches, standings, lineups, events, xG, and odds. It lacks detailed team or player profile endpoints, but for the apparent match-analysis focus, the coverage is strong with only minor gaps.