fpl
FPL MCP Server
claude mcp add --transport stdio singhgaurav10-fpl-mcp-server node server.js \ --env PORT="5000" \ --env NODE_ENV="production"
How to use
This MCP server provides an interface for interacting with Fantasy Premier League (FPL) data through the MCP protocol. Once running, clients can connect to the server to query and retrieve FPL-related resources such as player statistics, team data, fixtures, and other commonly requested endpoints that are exposed by the MCP layer of this project. The server acts as a bridge between your MCP client tooling and the underlying FPL data sources, returning structured responses suitable for integration into dashboards, bots, or analytics pipelines. To use, start the server with the configured command, then issue MCP requests against the fpl endpoint to fetch the data you need. Typical use cases include pulling current season player stats, upcoming fixtures, or historical performance summaries for reporting or automation tasks.
How to install
Prerequisites:
- Node.js (14.x or later) and npm installed on your machine.
- git (optional, for cloning the repository).
Step 1: Clone the repository
- git clone <repository-url>
- cd fpl-mcp-server
Step 2: Install dependencies
- npm install
Step 3: Configure environment (optional but recommended)
- PORT: Port to run the MCP server (default 5000)
- NODE_ENV: Set to production or development as needed
Step 4: Run the server
- npm start
- Or: node server.js
Step 5: Verify it's running
- Send a basic MCP ping or query to the server endpoint and ensure a valid MCP response is returned.
Additional notes
Notes and tips:
- Ensure your environment allows network access on the configured PORT.
- If you need to expose the MCP server publicly, consider reverse-proxying with a web server (e.g., Nginx) and enforcing TLS.
- If the server cannot start due to missing dependencies, run npm install to refresh node_modules.
- Customize environment variables as needed for production deployments (e.g., enabling caching, adjusting timeouts).
- The exact MCP endpoints and data schemas depend on the server implementation; refer to the codebase for the definitive set of resources exposed by the fpl MCP module.
