mcp-football

The MCP Football Server is a lightweight Node.js-based tool that exposes football data via the MCP (Model Context Protocol) JSON-RPC interface. It connects to the API-Football service to provide fixtures, standings, team and player information, transfers, injuries, and head-to-head stats. Clients can query the server over standard MCP JSON-RPC messages and receive structured data suitable for AI assistants or applications. The server is built with Node.js and TypeScript, uses the MCP SDK for stdio-based tool serving, and relies on node-fetch to call the external API, with Zod handling parameter validation. After building, a binary entry point is provided (main.js) that runs the compiled server and serves MCP commands over STDIN/STDOUT.

To use the server, start it with the Node entry point and then issue MCP commands from your client or application. If you’re integrating with Claude Desktop, configure your client to point at the built server binary and supply the required RapidAPI credentials. The server will respond with football data such as fixtures by date, league standings, team and player details, transfers, injuries, and head-to-head results.

Key capabilities include: retrieving fixtures by date, obtaining league standings, fetching team and player information, checking transfers and injuries, and obtaining head-to-head matchups. These tools are designed to be consumed by MCP-compliant clients or assistants.

Prerequisites:

• Node.js (14.x or newer) and npm installed on your system
• Access to a RapidAPI API-Football key (RAPIDAPI_KEY) and host (RAPIDAPI_HOST)

Installation steps:

1. Clone the repository git clone https://github.com/yalmeidarj/mcp-football-server.git cd mcp-football-server

2. Install dependencies npm install

3. Build for production (optional but recommended for production use) npm run build

4. Run in development npm run dev

5. Run in production npm start

Notes:

• The server exposes an MCP-compatible interface via STDIN/STDOUT. After building, use the provided entry point (build/main.js) to start the server as shown in the mcp_config example.
• Ensure your environment variables are set where the server expects them (see mcp_config for the required env vars).

Tips and known considerations:

• Environment variables: RAPIDAPI_KEY and RAPIDAPI_HOST are required to access the API-Football data provider.
• Build artifacts: The build step outputs to the build/ directory; the runtime entry is build/main.js.
• The server is designed to be MCP-compliant for stdio-based tool serving, so ensure your MCP client (or Claude Desktop config) is prepared to communicate via JSON-RPC over STDIN/STDOUT.
• If you modify the code or switch environments (e.g., different API providers), update env vars and rebuild accordingly.
• Common issues: missing API keys or incorrect host values will lead to request failures; verify credentials and network access.