FPL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getFixturesForGameweekC | Fetch fixtures for a specific gameweek |
| getLiveEventB | Fetch focused live stats for a gameweek. Optionally filter to specific players by providing elementIds array. |
| getEntryHistoryC | Fetch this and previous season performance of a team |
| getEntryTransfersC | Fetch all transfers of a team |
| getEntryPicksC | Fetch squad picks of a team for a specific week |
| getLeagueStandingsD | Fetch information about a league by ID |
| getLeagueStandingsPageB | Fetch a page of league standings for leagues with more than 50 teams |
| getRegionsB | Fetch FPL region list |
| getBestClassicPrivateLeaguesB | Fetch list of best classic private leagues |
| getPlayerDataB | Fetch all player data |
| getTeamDataC | Fetch all team data |
| getGameweekDataB | Fetch all gameweek data |
| getChipDataC | Fetch all chip data |
| getFixturesB | Fetch all FPL fixtures |
| getElementSummaryC | Fetch details for a specific player (element) |
| getEntryC | Fetch general info about a team by entry ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Every tool has a clearly distinct purpose targeting specific FPL resources like leagues, players, teams, fixtures, or gameweeks, with no overlap in functionality. The descriptions precisely indicate what each tool fetches, making it easy for an agent to select the correct one without confusion.
All tool names follow a consistent verb_noun pattern starting with 'get' followed by a descriptive noun phrase (e.g., getElementSummary, getFixturesForGameweek), with no deviations in style or convention. This predictability enhances usability and clarity across the entire set.
With 16 tools, the server is well-scoped for the FPL domain, covering a comprehensive range of data points from player details to league standings without being excessive. Each tool serves a specific, necessary function, making the count appropriate for thorough data retrieval in fantasy football.
The tool set provides complete coverage for fetching FPL data, including CRUD-like operations for players, teams, leagues, fixtures, and gameweeks, with no obvious gaps. It supports both general queries (e.g., getPlayerData) and specific ones (e.g., getElementSummary), ensuring agents can access all needed information without dead ends.