FPL MCP
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
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 |
|---|---|
| login_to_fplA | Open a browser to sign in to Fantasy Premier League and save the token. A real browser window opens on the FPL site. The user signs in there themselves; their password is never seen by this tool or the model. Once signed in, the session token is captured and stored for later calls. |
| get_my_teamA | Get an FPL team: starting XI, bench, captain, bank, value, and chips. |
| get_gameweek_statusA | Show the current, previous, and next gameweeks, plus the next deadline. |
| search_playersA | Find players by filters, best first. |
| compare_playersC | Compare two or more players side by side by name. |
| get_playerB | Detailed profile for one player: stats, status, and upcoming fixtures. |
| get_fixturesC | Upcoming fixtures and difficulty for a club (e.g. 'Arsenal' or 'ARS'). |
| blank_double_gameweeksA | List upcoming blank and double gameweeks by club. |
| team_newsB | Injury and availability news: who is injured, doubtful, or suspended, their chance of playing, and the official note. |
| get_league_standingsB | Show standings for a classic mini-league by its ID. |
| transfer_historyA | Show a team's transfers this season. Auto-detects your team if logged in. |
| suggest_transfersB | Suggest transfers that improve your squad over the next 3 gameweeks. |
| analyze_mini_leagueA | Spy on a classic mini-league: your rank, your edge, and the threats, compared against the ~10 managers above and below you. |
| make_transferA | Transfer one player out and another in (by name). |
| transfer_previewA | Show what a transfer would do (funds, position) WITHOUT submitting it. |
| set_captainA | Set your captain, and optionally your vice-captain (by name). |
| substituteA | Swap a bench player into the starting XI and move a starter to the bench. |
| play_chipB | Activate a chip, or cancel the active one. |
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 18 tools
Most tools target a distinct action and resource: search, compare, get profile, fixtures, transfers, chips, and squad moves are well separated. The main potential confusion is between get_league_standings and analyze_mini_league, which both deal with mini-league data, though their descriptions indicate different scopes.
There is a clear majority pattern of imperative get_/set_/make_/play_ verbs, but several names are noun phrases instead, such as team_news, transfer_history, transfer_preview, and blank_double_gameweeks. The convention is consistent enough to be readable, but it is not uniformly verb_noun.
18 tools is on the heavier end, but the FPL domain is broad and each tool serves a distinct part of the workflow: login, squad, players, fixtures, news, transfers, chips, and leagues. A few could arguably be folded together, but the count feels justified rather than bloated.
The tool surface covers the core FPL lifecycle: authentication, team viewing, player research, fixture difficulty, injuries, league standings, mini-league analysis, transfer history/suggestions/preview/execution, captain selection, substitutions, and chips. There are no obvious dead ends or missing domain-critical operations.