Meituan MCP integration for AI agents.
Connect AI agents to Meituan through 1 structured actions, including query travel. Review authentication, inputs, workflows, and safety guidance.
- ACTION CONTRACTS
- 1
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Meituan integration exposes
The Meituan Agent App exposes 1 provider-backed actions for productivity and location work. Its current contract lets an authorized agent query meituan travel for flights, trains, hotels, attractions, itineraries, local transportation, and other travel information using natural language. requests may take up to two minutes, so use a caller timeout longer than 120 seconds. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. 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 Meituan account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Meituan capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
query_travelREADQuery Meituan Travel for flights, trains, hotels, attractions, itineraries, local transportation, and other travel information using natural language. Requests may take up to two minutes, so use a caller timeout longer than 120 seconds.
INPUTS: query / city / originQuery
INPUT CONTRACTS
Know what the action needs before it runs.
query_travel
queryREQUIRED- The user's travel question or request, including useful details such as dates, origin, destination, budget, and number of travelers.
cityOPTIONAL- The user's current city or the city used as context for the travel query. Defaults to Beijing when omitted.
originQueryOPTIONAL- The complete original user request used for Meituan attribution and analytics. Defaults to query when omitted.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Query Travel
Query Meituan Travel for flights, trains, hotels, attractions, itineraries, local transportation, and other travel information using natural language. Requests may take up to two minutes, so use a caller timeout longer than 120 seconds. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
query_travelVerify with Query Travel
Query Meituan Travel for flights, trains, hotels, attractions, itineraries, local transportation, and other travel information using natural language. Requests may take up to two minutes, so use a caller timeout longer than 120 seconds. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
query_travelSAFETY BOUNDARY
Operate Meituan with explicit limits
- Authorize Meituan with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Meituan 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 Meituan rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Meituan task completed successfully.
CONNECTION MODEL
API key
Meituan personal developer Token used to query Meituan Travel. Complete personal developer verification and create a Token at https://developer.meituan.com/zh/v2/dev/token. The Token is verified when the first travel query runs because Meituan does not provide a lightweight validation endpoint.
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
- 1
- 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 Meituan.