MCP server for Fantasy Premier League — read your team, analyse players, and manage transfers.
FPL MCP has 18 tools with consistent naming (verb_noun pattern) and reasonable descriptions (avg ~120 chars). However, critical gaps exist: parameter descriptions are sparse or missing entirely (e.g., search_players has 6 params but only 4 have descriptions; team_news has 2 params with minimal guidance). Output schemas are completely undocumented, no tool declares what fields it returns, forcing LLMs to infer structure from unstructured text responses. Error handling is absent: tools return plain strings with no guidance on recovery or retry logic. Security concern: login_to_fpl stores tokens but no documentation on token lifecycle, expiry, or revocation. Composition is reasonable (single responsibility per tool), but many tools lack the parameter constraints (enums, ranges) needed for reliable LLM invocation.
Spy on a classic mini-league: your rank, your edge, and the threats, compared against the ~10 managers above and below you.
List upcoming blank and double gameweeks by club.
Compare two or more players side by side by name.
Upcoming fixtures and difficulty for a club (e.g. 'Arsenal' or 'ARS').
Show the current, previous, and next gameweeks, plus the next deadline.
Show standings for a classic mini-league by its ID.
Get an FPL team: starting XI, bench, captain, bank, value, and chips.
Output schemas completely undocumented. No tool declares return type, field names, or structure. LLMs must infer from unstructured text responses, causing parsing errors and wasted tokens.
Parameter descriptions missing or incomplete. search_players has 6 params but only 4 have descriptions; team_news has 2 params with minimal guidance. LLMs cannot infer valid values or constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
Detailed profile for one player: stats, status, and upcoming fixtures.
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.
Transfer one player out and another in (by name).
Activate a chip, or cancel the active one.
Find players by filters, best first.
Set your captain, and optionally your vice-captain (by name).
Swap a bench player into the starting XI and move a starter to the bench.
Suggest transfers that improve your squad over the next 3 gameweeks.
Injury and availability news: who is injured, doubtful, or suspended, their chance of playing, and the official note.
Show a team's transfers this season. Auto-detects your team if logged in.
Show what a transfer would do (funds, position) WITHOUT submitting it.
No enum constraints on string parameters. 'position' in search_players accepts free-form strings instead of enum [GKP, DEF, MID, FWD]. 'sort_by' accepts free-form instead of enum [points, form, price, ownership, goals, assists]. LLMs will hallucinate invalid values.
No error handling or recovery guidance. Tools return plain strings with no indication of success/failure, retryability, or next steps. E.g., 'No player found matching X' gives no guidance on how to recover.
Token lifecycle and security undocumented. login_to_fpl stores tokens but no description of expiry, revocation, or how stale tokens are handled. Agents may retry with expired credentials indefinitely.