The design detail worth noticing is that you ask what cuisines and cities exist before searching by them, so a query is built from values the dataset actually holds rather than from a guess at spelling. Restaurant filters must carry real values — the tool's own instruction is to omit a filter rather than pass it empty.
A query layer over the Michelin restaurant dataset. Five of the six tools return the dimensions you would filter on — cities, countries, cuisines, awards and facilities — ordered by how many restaurants each holds, and the sixth returns restaurants filtered by them. Lists page with an offset rather than returning everything at once.
- Every city, ordered by restaurant count, paged by offset
- Every country, ordered the same way
- Every cuisine, ordered the same way
- Every award, ordered by ranking
- Every facility and service, ordered by restaurant count
- Restaurants returned against whichever of those filters you supply, or all of them with the filters omitted
Npx on your PATH — the documented setup bridges to the SSE endpoint at https://michelin-mcp.deno.dev through supergateway. No account and no key.
One command — npx supergateway --sse https://michelin-mcp.deno.dev