The endpoint
A remote Model Context Protocol server (stateless JSON-RPC 2.0 over HTTP):
https://airportdropoffcharges.co.uk/mcp
It exposes the whole dataset as callable tools, each returning verified, dated, self-citing answers.
Add it to Claude
On a Claude plan that supports custom connectors:
- Open Settings → Connectors (or Feature settings → Connectors).
- Choose Add custom connector.
- Paste the URL
https://airportdropoffcharges.co.uk/mcpand save. - Start a chat, enable the connector, and ask something like "What's the drop-off charge at Bristol Airport?" — Claude will call the tool and answer with the verified figure and source.
The tools
list_airportsEvery airport with its fee, free-time window and whether a free alternative exists.
get_airport_charge (airport)Full verified detail for one airport by name or IATA code — fee, overstay, payment, free alternative, on-the-ground notes, rail link, verification date and source.
compare_airports (airports[])Two or more airports side by side.
summary_statsAverage, highest, which airports are free, and which have no free alternative.
For developers & other clients
The endpoint speaks plain JSON-RPC 2.0, so any MCP-compatible client (or a direct HTTP call) works. List the tools:
curl -s https://airportdropoffcharges.co.uk/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Call one:
curl -s https://airportdropoffcharges.co.uk/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
"params":{"name":"get_airport_charge","arguments":{"airport":"Heathrow"}}}'
A GET to the same URL returns a short JSON description of the server and its tools.
ChatGPT & others
OpenAI's Apps SDK is built on MCP, so this same server is the backbone for a ChatGPT app (which is a developer submission through OpenAI, not an instant add). Cursor, and other MCP-aware tools can point at the endpoint directly. For assistants that don't take custom connectors (Perplexity, Gemini), the AI data page, llms.txt and the open JSON/CSV are the route in.
Method & corrections
Every figure on this page is checked against the airport's own published charges and stamped with the date we checked it. We re-verify the full dataset quarterly, and after any reported change — see how we work and who maintains it.
Spotted an error? Email hello@airportdropoffcharges.co.uk — corrections are made visibly and dated. The dataset behind this page is free to reuse with attribution: JSON · CSV (CC BY 4.0).