Restaurant locator and footprint mapping
Mit McDonald's-Endpunkten verwandelst du restaurant locator and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn McDonald's public restaurant and menu data into structured JSON — restaurant locations across ten markets with hours and amenities, menu categories and items across eight markets, one US restaurant's real eat-in/pickup/delivery prices, and full per-item nutrition detail (21+ nutrient values, allergens, ingredients) for up to 20 items in one call. Credential-free.
Find McDonald's restaurants worldwide, browse menu categories, get one US restaurant's real prices, and pull full per-item nutrition detail as structured JSON.
Endpunkt-Familien
6
Dokumentierte Parameter
19
Beispiele
6
Live-Katalog-Snapshot
Aktive Endpunkte
6
Methoden
GET
Pflichtparameter
12
Schema-Referenzen
6
{
"platform": "McDonald's",
"endpoint": "mcdonalds-restaurants",
"method": "GET",
"path": "/mcdonalds/restaurants",
"auth": "apiKey"
}Use Cases
Find McDonald's restaurants worldwide, browse menu categories, get one US restaurant's real prices, and pull full per-item nutrition detail as structured JSON.
Mit McDonald's-Endpunkten verwandelst du restaurant locator and footprint mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit McDonald's-Endpunkten verwandelst du real-price monitoring for us restaurants in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit McDonald's-Endpunkten verwandelst du menu and nutrition data for diet and health apps in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit McDonald's-Endpunkten verwandelst du multi-market menu coverage research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-McDonald's-Endpunktkatalog — 6 Endpunkte, 19 dokumentierte Request-Parameter und 6 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
6 documented McDonald's endpoints, grouped into 6 request families — Categories, Item and Item List, plus 3 more.
19 request parameters are documented across those McDonald's endpoints, 12 of them required — the full input contract is public before you write any integration code.
6 of the 6 McDonald's endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
McDonald's endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
6 hosted MCP tools back the McDonald's endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/mcdonalds/categories
/mcdonalds/item
/mcdonalds/item-list
/mcdonalds/menu
/mcdonalds/restaurant-menu
/mcdonalds/restaurants
Endpunktkatalog
/mcdonalds/restaurantsReturns McDonald's restaurants near a latitude/longitude, in any of ten markets. Each restaurant carries its store id, name, street address, city, state, postal code, phone, coordinates, timezone, open status, today's dining and drive-thru hours, the full published week of hours, and McDonald's own amenity codes (for example DRIVETHRU, WIFI, MOBILEOFFERS, GIFTCARDS). A delivery deep link is included where McDonald's publishes one; note it points at a third-party delivery platform. A coordinate with no McDonald's nearby returns an empty list rather than an error. Set country to search outside the United States -- the locator covers more markets than the menu and item endpoints do, so a country valid here is not necessarily valid there.
MCP-Tool mcdonalds_restaurants
/mcdonalds/restaurant-menuReturns one restaurant's full menu with real prices: item name, image and independently-priced eat-in, pickup and delivery listings, since a McDonald's restaurant genuinely sells a different catalog (and different prices) per channel -- delivery is typically marked up over eat-in/pickup, and some items are channel-exclusive. Where McDonald's publishes a curated substitute or add-on list for an item (a meal's drink upgrade, a dip-able item's sauce choices), each real alternative is included with its own eat-in/pickup price delta -- plain entree or side substitution is not covered, since McDonald's does not publish a curated candidate list for it. This is the only endpoint in this family that publishes prices; every other McDonald's endpoint's source never does. US restaurants only. The store id comes from GET /mcdonalds/restaurants' store_id field.
MCP-Tool mcdonalds_restaurant_menu
/mcdonalds/categoriesReturns one market's McDonald's menu categories -- 13 in the United States at time of writing, including breakfast, burgers, chicken-and-fish-sandwiches, mcnuggets-and-mccrispy-strips, snack-wrap, fries-sides, happy-meal, sweets-treats, mccafe-coffees, drinks, sauces-and-condiments and the two value menus; other markets publish their own, from 6 in Switzerland to 17 in Australia. Each entry's slug is the value GET /mcdonalds/menu takes. Slugs are not portable between markets, so pass the same country back. Eight markets publish a reachable menu, fewer than the ten the restaurant locator covers.
MCP-Tool mcdonalds_categories
/mcdonalds/menuReturns the items in one McDonald's menu category: each item's numeric id, name, product page URL and image. The item id is what GET /mcdonalds/item takes for full nutrition. Category slugs come from GET /mcdonalds/categories and must be paired with the country they came from -- both slugs and item ids are market-specific. Prices are not available; McDonald's does not publish them on this surface. A calorie label is included per item where the category page prints one, which is often blank.
MCP-Tool mcdonalds_menu
/mcdonalds/itemReturns one McDonald's item's published nutrition detail: the full per-serving nutrient list (calories, protein, carbohydrates, total and saturated fat, trans fat, cholesterol, sodium, fibre, sugars, vitamins and minerals -- 21 values for a Big Mac), each with a stable machine key, a unit and a percent-daily-value where McDonald's prints one; plus the item's marketing description, allergen statement, full ingredient statement and image. Item ids come from GET /mcdonalds/menu and are market-specific, so pass the same country back. Seven markets serve this endpoint, fewer than the eight publishing a menu -- Great Britain has a menu but no nutrition surface. Combo meals legitimately carry no nutrient list. Prices are not available on this surface.
MCP-Tool mcdonalds_item
/mcdonalds/item-listReturns the same published nutrition detail as GET /mcdonalds/item for up to 20 items in one call, plus the per-component ingredient and allergen breakdown that the single-item endpoint does not expose -- a composite item's overall allergen statement is the union of its parts' (a burger's bun, patty, cheese and condiment each carry their own ingredient statement and allergens), so this is the source to use when the full breakdown matters, not just the item-level summary. Item ids come from GET /mcdonalds/menu and are market-specific, so pass the same country back. The response echoes the requested ids so a caller can tell which ones McDonald's returned nothing for.
MCP-Tool mcdonalds_item_list
Verwandte APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
So scrapst du McDonald's
Crawlora's McDonald's endpoints return normalized public McDonald's data as JSON with one API key — no McDonald's account required. Category slugs and item ids are market-specific, so always pass the same country back to the endpoint that returned them.
Pass a latitude and longitude to /mcdonalds/restaurants for nearby locations in any of ten markets — each with address, phone, coordinates, today's dining and drive-thru hours, the full published week, and McDonald's own amenity codes (DRIVETHRU, WIFI, MOBILEOFFERS, and more).
Pass a store_id from /mcdonalds/restaurants to /mcdonalds/restaurant-menu for that restaurant's full menu with independently-priced eat-in, pickup, and delivery listings — a McDonald's genuinely sells a different catalog and price per channel, with delivery typically marked up and some items channel-exclusive. US restaurants only, and the only McDonald's endpoint that publishes prices.
Call /mcdonalds/categories for one market's menu categories (13 in the US, from 6 to 17 elsewhere), then pass a category slug to /mcdonalds/menu for that category's items, ids, and product page URLs.
Pass an item id from /mcdonalds/menu to /mcdonalds/item for one item's full nutrition, or /mcdonalds/item-list for up to 20 items in one call, including the per-component ingredient and allergen breakdown a single-item lookup does not expose.
The restaurant locator covers more markets (ten) than the menu and nutrition endpoints (eight, and seven for nutrition) — a country valid for /mcdonalds/restaurants is not necessarily valid for /mcdonalds/menu or /mcdonalds/item, and menu slugs and item ids never carry over between markets.
FAQ
Call /mcdonalds/restaurants with a coordinate for nearby locations, /mcdonalds/restaurant-menu for one US restaurant's real prices, /mcdonalds/categories and /mcdonalds/menu for one market's menu, or /mcdonalds/item and /mcdonalds/item-list for full nutrition detail — all return structured JSON with one API key.
Yes, for US restaurants — /mcdonalds/restaurant-menu returns real eat-in, pickup, and delivery prices for one restaurant by store_id, since a McDonald's sells a different catalog and price per channel. Every other McDonald's endpoint (/mcdonalds/menu, /mcdonalds/item) never publishes prices, only nutrition, images, and product URLs.
The restaurant locator covers ten markets; the menu catalog covers eight (Great Britain has a menu but no nutrition surface); nutrition covers seven; real pricing (/mcdonalds/restaurant-menu) is US-only. Pass the same country to related calls — category slugs and item ids are market-specific and don't carry over.
Combo meals legitimately carry no nutrient list on McDonald's own published data — only individual items do.