The expensive part of FOI is not writing the request — it is finding out whether the authority has already answered it and what happened when somebody tried. Searching the responses first turns that into a lookup, and the drafting tools pick up where the search stops.
A research interface to WhatDoTheyKnow, the UK's largest FOI request platform. It searches requests and responses, resolves public authorities to the slugs the other tools take, reads a request's full correspondence history, and helps put a new request together.
- Full-text search across FOI requests and responses, with structured expressions such as status:successful or body:'Liverpool City Council'
- UK public authorities searched by name, returning the slug the other tools need, plus the detail behind one
- A request's event timeline — sent, response, clarification
- The full public request JSON: status, authority, requester, correspondence events, and attachment metadata where exposed
- A named user's requests and their feed
- A URL built for a new request, a record created for it, and its state updated as it moves
Nothing to install on the hosted path — the endpoint is https://whatdotheyknow-mcp.fly.dev/mcp. Locally it runs under uvx whatdotheyknow-mcp. It reads WhatDoTheyKnow's public data, with search going through the site's Atom feed.
One command — npx -y mcp-remote https://whatdotheyknow-mcp.fly.dev/mcp
