McDonald's China MCP integration for AI agents.
Connect AI agents to McDonald's China through 7 structured actions, including get cities, get menu, and get product detail. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the McDonald's China integration exposes
The McDonald's China Agent App exposes 7 provider-backed actions for location and data work. Its current contract lets an authorized agent get mcdonald's china cities that support restaurant and menu lookup, get a mcdonald's china store menu for an order type, daypart, and sales channel, and get detailed mcdonald's china menu product information. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected McDonald's China account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real McDonald's China capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_citiesREADGet McDonald's China cities that support restaurant and menu lookup.
INPUTS: getCurrent
get_menuREADGet a McDonald's China store menu for an order type, daypart, and sales channel.
INPUTS: storeCode / channelCode / orderType / dayPartCode / beCode
get_product_detailREADGet detailed McDonald's China menu product information.
INPUTS: code / storeCode / channelCode / daypartCode / orderType
get_storeREADGet one McDonald's China store by store code.
INPUTS: storeCode
get_store_businessREADGet McDonald's China business details for a store business entity code.
INPUTS: beCode / date / isGroupMeal / time
search_productsREADSearch McDonald's China menu products for one store, daypart, and order type.
INPUTS: keyword / storeCode / daypartCode / orderType / beCode
search_storesREADSearch McDonald's China stores by delivery address, city, location, keyword, or order filters.
INPUTS: addressId / beType / cityCode / date / distance
INPUT CONTRACTS
Know what the action needs before it runs.
get_cities
getCurrentOPTIONAL- McDonald's China flag value: 0 for no, 1 for yes.
get_menu
storeCodeREQUIRED- Store code.
channelCodeREQUIRED- Sales channel code.
orderTypeREQUIRED- Order type.
dayPartCodeREQUIRED- Daypart code.
beCodeOPTIONAL- A McDonald's China query parameter value.
get_product_detail
codeREQUIRED- Product code.
storeCodeREQUIRED- Store code.
channelCodeREQUIRED- Sales channel code.
daypartCodeREQUIRED- A McDonald's China query parameter value.
orderTypeREQUIRED- A McDonald's China query parameter value.
get_store
storeCodeREQUIRED- Store code.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Cities
Get McDonald's China cities that support restaurant and menu lookup. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_citiesVerify with Get Menu
Get a McDonald's China store menu for an order type, daypart, and sales channel. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_menuSAFETY BOUNDARY
Operate McDonald's China with explicit limits
- Authorize McDonald's China with Custom credentials and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned McDonald's China data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in McDonald's China rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the McDonald's China task completed successfully.
CONNECTION MODEL
Custom credentials
McDonald's China uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by McDonald's China.