football-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_HOST | No | Host to bind the HTTP server to when running in HTTP mode. Default is 127.0.0.1. | |
| MCP_HTTP_PORT | No | Port to bind the HTTP server to when running in HTTP mode. Default is 3333. | |
| MCP_HTTP_TOKEN | No | Authentication token for HTTP mode, used in the URL path. Equivalent to --token. | |
| FIVEDOLLARFOOTBALL_API_KEY | Yes | Your API key from 5dollarfootballapi.com. Required for all requests. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_fixturesA | List football fixtures for a calendar day (UTC). Defaults to today. Includes live scores, corners and cards for each match. |
| get_fixtureA | Get one fixture by id, optionally with the event timeline (goals, cards, corners) and match statistics. |
| get_fixture_oddsA | Current betting odds for a fixture: 1x2, Asian handicap, goal line, corner line, card lines, BTTS — per bookmaker. |
| get_odds_historyA | Full price-movement history (every recorded tick) for one fixture and market. Each tick has the price, match minute, running score and UTC timestamp. |
| get_bookmakersA | List the bookmaker slugs usable in the odds tools. |
| get_standingsA | League table for a league and season. type "corner" and "card" return corner/card standings instead of points. |
| search_leaguesA | Find leagues by name, country or popularity. Use this to discover league ids. |
| search_countriesA | List countries (optionally filtered by name substring), for use with search_leagues. |
| get_league_fixturesB | A league season's fixtures and results. |
| get_team_fixturesB | A team's matches home or away, most recent first. |
| get_account_statusA | Your API plan, usage and rate-limit state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| todays-briefing | Summarize the most interesting fixtures of a day: kickoff times, live scores, standout results. |
| odds-movement-report | Analyze how the betting market moved on one fixture: opening vs closing, key swings, in-play reaction. |
| corner-scout | Scout a league's corner tendencies from its corner standings and recent results. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| popular-leagues | The popular football leagues with their ids, for use with the league tools. |
| bookmakers | The bookmaker slugs accepted by the odds tools. |
TDQS
Scored across 11 tools
Each tool targets a distinct resource/scope: fixtures are separated by day, id, league, and team; odds, standings, searches, and account status are clearly distinct. The descriptions make the boundaries between the fixture-listing tools explicit enough that an agent should not misselect.
All tools follow a consistent snake_case action_noun pattern, with get_ used for retrieval and search_ used specifically for discovery. This is a predictable and readable convention across the entire toolset.
11 tools is a well-scoped count for a football data and odds API. Each tool covers a meaningful area such as fixtures, standings, odds, discovery, or account status without feeling bloated or sparse.
Core workflows around fixtures, standings, odds history, and league/country discovery are covered well. The main gap is the lack of a team search or direct team lookup, which makes get_team_fixtures harder to use unless team IDs are first extracted from fixture data.