fotmob-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOTMOB_X_MAS | No | Optional header value for FotMob requests, obtained from browser DevTools | |
| FOTMOB_BASE_URL | No | Override the default FotMob base URL | |
| FOTMOB_CACHE_DIR | No | Change the local cache directory | |
| FOTMOB_CACHE_TTL_SECONDS | No | Change the cache lifetime in seconds |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_fotmob_routesB | List the verified FotMob route inventory, optionally filtered by a keyword. |
| fetch_fotmob_routeC | Fetch one of the verified FotMob JSON routes through the shared FotMob client. |
| search_fotmobC | Fetch FotMob search suggestions for a term. |
| get_match_detailsB | Fetch FotMob match details from a match id or FotMob match URL. Fresh data is fetched by default. |
| get_match_livetickerA | Fetch FotMob live ticker/commentary events from a match id or FotMob match URL. Fresh data is fetched by default. |
| get_league_top_statsB | Fetch top league player/team stats and resolve FotMob internal season ids automatically. |
| get_live_fixturesC | Fetch live league fixtures from the league payload's live fixture poll link. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| FotMob API Reference | |
| FotMob Route Catalog | |
| FotMob Reusable Prompt |
TDQS
Scored across 7 tools
Each tool targets a distinct data source or action: fetching specific routes, league stats, live fixtures, match details, liveticker, listing routes, and searching. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_match_details, list_fotmob_routes). The naming is predictable and easy to understand.
Seven tools is well-scoped for a sports data API, covering common queries without being excessive. Each tool serves a clear need.
The tool set covers search, live data, match details, and league stats. The generic fetch_fotmob_route allows access to any API endpoint, compensating for missing specific tools like team info or league tables.