Back to MCP Directory

Fantasy Pl

Model Context Protocol moderate risk

Fantasy Pl

Provides read-only access to Fantasy Premier League data, enabling analysis and decision-making within MCP-compatible clients; authentication enables access to user-specific data.

Connections & Capabilities

Connects To

GitHub

Capabilities

read

Quickstart

Install

pip install fpl-mcp

Config

{
  "mcpServers": {
    "fantasy-pl": {
      "command": "python",
      "args": ["-m", "fpl_mcp"]
    }
  }
}

Exposed MCP Tools (11)

safe

get_gameweek_status

Retrieves information about the current, previous, and next gameweeks.

Read-only operation; no side effects.

safe

analyze_player_fixtures

Analyzes upcoming fixtures for a specific player, providing difficulty ratings.

Read-only operation; no side effects.

safe

get_blank_gameweeks

Provides information about upcoming blank gameweeks.

Read-only operation; no side effects.

safe

get_double_gameweeks

Provides information about upcoming double gameweeks.

Read-only operation; no side effects.

safe

analyze_players

Filters and analyzes FPL players based on multiple criteria.

Read-only operation; no side effects.

safe

analyze_fixtures

Analyzes upcoming fixtures for players, teams, or positions.

Read-only operation; no side effects.

safe

compare_players

Compares multiple players across various metrics.

Read-only operation; no side effects.

safe

check_fpl_authentication

Checks if FPL authentication is working correctly.

Read-only operation; no side effects.

safe

get_my_team

Retrieves and displays the user's authenticated FPL team.

Read-only operation; requires authentication.

safe

get_team

Retrieves and displays any FPL team with a specific ID.

Read-only operation; requires authentication.

safe

get_manager_info

Retrieves and displays FPL manager details.

Read-only operation; requires authentication.

Safety Assessment

This MCP server is generally safe for read-only access to FPL data. The primary risk lies in the handling of user credentials. Ensure proper configuration and secure storage of credentials to mitigate potential risks. Avoid using on untrusted systems.

Primarily read-only access to FPL data.
Authentication is required for accessing user-specific data, adding a layer of security.
No inherent risk of data deletion or modification of the FPL service itself.
Clear documentation on authentication and configuration.

Requires user to input FPL credentials (email, password, team ID), which could be compromised if stored insecurely.
Improper handling or storage of credentials could lead to unauthorized access to user's FPL account.
Reliance on the FPL API, which is undocumented and subject to change, potentially breaking functionality.
Potential for information disclosure if sensitive data is inadvertently exposed through the MCP interface.