Restaurant locator and footprint mapping
McDonald'sエンドポイントを使えば、「Restaurant locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
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.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
19
サンプル数
6
ライブカタログスナップショット
稼働エンドポイント
6
メソッド
GET
必須パラメータ
12
スキーマ参照
6
{
"platform": "McDonald's",
"endpoint": "mcdonalds-restaurants",
"method": "GET",
"path": "/mcdonalds/restaurants",
"auth": "apiKey"
}ユースケース
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.
McDonald'sエンドポイントを使えば、「Restaurant locator and footprint mapping」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
McDonald'sエンドポイントを使えば、「Real-price monitoring for US restaurants」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
McDonald'sエンドポイントを使えば、「Menu and nutrition data for diet and health apps」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
McDonald'sエンドポイントを使えば、「Multi-market menu coverage research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のMcDonald'sエンドポイントカタログから取得しています（エンドポイント6件、ドキュメント化されたリクエストパラメータ19個、公開レスポンススキーマ6件）。DocsとPlaygroundが参照しているカタログと同じものです。
McDonald'sのエンドポイントは6件、6つのリクエストファミリーに分類されています（Categories、Item、Item Listほか3件）。
これらのMcDonald'sエンドポイントには19個のリクエストパラメータがドキュメント化されており、うち12個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
6件のMcDonald'sエンドポイントのうち6件が実際のサンプルレスポンスを、6件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
McDonald'sのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
McDonald'sのエンドポイントは6個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/mcdonalds/categories
/mcdonalds/item
/mcdonalds/item-list
/mcdonalds/menu
/mcdonalds/restaurant-menu
/mcdonalds/restaurants
エンドポイントカタログ
/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ツール 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. 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ツール 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ツール 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ツール 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ツール 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ツール mcdonalds_item_list
関連API
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.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
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.