Connect AI to your football data with MCP
Use the Pro-plan read-only MCP connection, review consent and available tools, and keep AI client access separate from billing and account controls.
Step 1: Pro access
Eligible active account
Step 2: Consent
Approve a client connection
Step 3: Tools
Discover read-only football operations
Step 4: Revoke
Control the connection from your account
Use MCP for football retrieval, not account administration
The Model Context Protocol lets a compatible AI client request football data through documented tools. FootballAPI.net MCP access requires active Pro-plan API access and MCP enabled for the account.
The connection is read-only football access. It does not give the client your support inbox, account settings, key-management controls or billing operations. Tool availability follows the actual enabled football services, not a speculative list of every possible feed.
Start from Connect AI in your dashboard
Open Connect AI and use the server address and connection instructions shown there. For a client supporting the authorisation flow, sign in, review the consent screen, choose the appropriate active key and approve only the client you intend to connect.
For clients configured with a key header, keep that credential in the client's private configuration, not in a public project file. Follow the current MCP reference for supported client examples and protocol details rather than assuming every AI product implements the same flow.
Discover the actual tools before requesting data
Use the server's tools/list result as the authoritative tool catalogue. Map tool arguments to the same competition, team, player and static match IDs used by the REST API.
A capable language model can still choose an incorrect ID or misread an empty result. Ask the client to preserve actual dates and source record context, and do not treat a fluent answer as evidence that a field was present.
Share the same request budget deliberately
Successful football tool calls share the account's Pro allowance of 250,000 successful requests per UTC day. Paid GBP overages are £0.002 per additional successful request; existing EUR contracts retain their currency. Protocol discovery does not consume feed usage.
Tell your client to reuse retrieved records when answering follow-up questions about the same snapshot rather than repeatedly requesting identical data. An automated loop can consume requests quickly even when only one person is using it.
Review and revoke access when it is no longer needed
Manage connections and linked keys in your account. Revoking a connection or the relevant key stops new authorised access through it. Review permissions before connecting a different client.
The client's handling of returned data is governed by its own configuration and terms. Do not include payment details or unrelated personal information in football queries, and keep your public Ask AI product-help chat separate from an authenticated MCP data connection.
Related tutorials
Account and support / 8 min
Manage plans, trials, API keys and daily usage
Understand GBP plans, Starter's seven-day trial, daily allowances, metered overages, league selection and safe account support workflows.
Getting started / 8 min
Understand football IDs and response shapes
Learn static fixture IDs, competition and stage mappings, object-or-array collections and null-safe normalisation for football API responses.
Performance and operations / 9 min
Diagnose API errors and missing football data
Handle authentication, entitlement, validation, rate limits, temporary failures and empty collections with bounded retries and useful diagnostics.