Bring Food Delivery
to CrewAI
Create your Vinkius account to connect Meituan Waimai to CrewAI and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
Compatible with every major AI agent and IDE
What is the Meituan Waimai MCP Server?
Connect your Meituan Waimai (美团外卖) restaurant operations to any AI agent and transform your delivery management through natural conversation. Meituan Waimai is China's largest food delivery platform, handling millions of daily orders across hundreds of thousands of restaurants.
What you can do
- Order Management — Retrieve detailed order information, list orders by status (pending, confirmed, delivering, completed, cancelled)
- Order Lifecycle Control — Confirm new orders, mark orders as delivering, complete deliveries, or cancel with explanations
- Refund Processing — Approve or reject customer refund requests with detailed reasoning and order verification
- Restaurant Information — Query restaurant details including ratings, addresses, business hours, and delivery coverage
- Menu Management — List full restaurant catalogs, filter by category, view prices, descriptions, and stock levels
- Stock Control — Update item availability in real-time, mark items as sold out, or replenish inventory
- Delivery Tracking — Mark orders as out for delivery with rider information for customer transparency
How it works
- Subscribe to this server
- Enter your Meituan Waimai App ID and App Secret
- Start managing your restaurant operations from Claude, Cursor, or any MCP-compatible client
Your AI agent becomes your restaurant operations manager, handling order confirmations, monitoring stock levels, processing refunds, and optimizing your menu — all through conversational commands.
Who is this for?
- Restaurant Owners — Monitor incoming orders, manage menus, and handle refunds without logging into the merchant dashboard
- Multi-Location Operators — Query order volumes and restaurant info across multiple POIs from a single AI interface
- Kitchen Staff — Check order details, confirm new orders, and mark items as sold out when ingredients run low
- Customer Service — Track order status, investigate refund claims, and resolve delivery issues quickly
Built-in capabilities (10)
Requires a cancellation reason explaining why the order is being cancelled (e.g., "restaurant closed", "item out of stock", "unable to prepare"). The order must be in a cancellable state (not already completed or delivered). Use carefully as cancellations impact merchant ratings and customer experience. Cancel a Meituan delivery order with a reason
This is the final state in the order lifecycle and indicates the customer has received their food. Should only be called after the delivery rider has confirmed drop-off or the customer has picked up the order. Triggers payment settlement to the merchant. Mark a Meituan delivery order as completed
This transitions the order to confirmed status and begins the preparation workflow. Required step before marking the order as delivering. Use the order ID from the order list and the restaurant POI ID. Essential for acknowledging new orders and starting the fulfillment process. Confirm a pending Meituan delivery order
Use the order ID obtained from the order list to track specific orders, verify order contents, check delivery addresses, or investigate customer complaints. Essential for order management and customer service operations. Get detailed information about a specific Meituan delivery order
Filter by order status: 1=待确认 (pending confirmation), 3=已确认 (confirmed), 5=配送中 (delivering), 7=已完成 (completed), 8=已取消 (cancelled). Pagination uses page number and limit parameters. Critical for monitoring incoming orders, tracking order volume, and managing the order pipeline. List orders for a Meituan restaurant with optional status filter
Use the POI ID (Point of Interest identifier) to get restaurant details before managing orders, verifying delivery coverage, or checking business hours. Essential for multi-restaurant operators managing multiple POIs. Get detailed information about a Meituan restaurant/POI
When rejecting, provide a reason explaining the refusal. Refund requests typically come with customer explanations and evidence. Use order details to verify the claim before making a decision. Approved refunds are processed back to the customer's original payment method. Approve or reject a refund request for a Meituan order
Optionally filter by category ID to get items from a specific menu section (e.g., appetizers, mains, drinks). Critical for inventory management, price updates, and menu optimization. Returns stock quantities to help identify low-stock items. List menu items for a Meituan restaurant
Optionally includes delivery rider name and phone number for customer tracking. Use this for self-delivery orders where the restaurant manages their own riders. For Meituan-managed delivery, the platform handles this automatically. Mark a Meituan order as being delivered (out for delivery)
Use this to mark items as sold out (stock=0) when ingredients run out, or replenish stock when new inventory arrives. Stock changes immediately reflect on the customer-facing menu. Essential for preventing orders for unavailable items and maintaining accurate inventory. Food ID is obtained from the list_menus tool. Update stock quantity for a menu item in Meituan
Why CrewAI?
When paired with CrewAI, Meituan Waimai becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Meituan Waimai tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Meituan Waimai in CrewAI
Why run Meituan Waimai with Vinkius?
The Meituan Waimai connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.




Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Meituan Waimai using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Meituan Waimai and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Meituan Waimai to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Meituan Waimai for CrewAI
Every request between CrewAI and Meituan Waimai is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
How do I get my Meituan Waimai App ID and App Secret?
Log in to the Meituan Waimai Developer Console, navigate to API Documentation > Access Guide, and register your application. You'll receive an App ID and App Secret. Make sure your application has the required API permissions for order management, menu access, and refund handling. The signature algorithm uses MD5 hashing of sorted parameters combined with your App Secret.
What's the order lifecycle in Meituan Waimai?
The typical order flow is: 1) Pending (待确认, status=1) — Customer placed order, awaiting merchant confirmation. 2) Confirmed (已确认, status=3) — Merchant accepted the order, kitchen starts preparation. 3) Delivering (配送中, status=5) — Food is out for delivery with rider. 4) Completed (已完成, status=7) — Customer received the order, payment settled. 5) Cancelled (已取消, status=8) — Order was cancelled by merchant or customer. At each stage, you can query details, and merchants can confirm, mark delivering, or complete the order.
How do I handle stock management and sold-out items?
Use the update_stock tool to set stock quantities for menu items. Set stock=0 to mark an item as sold out (it will immediately disappear from the customer menu). Set a positive number to replenish stock. Get the food ID from the list_menus tool first. This is critical during peak hours when ingredients run out — quickly updating stock prevents customers from ordering unavailable items and reduces refund requests.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
ZoomInfo
8 toolsEquip your AI agent with direct access to ZoomInfo — search company and contact records, enrich lead data, and build prospect lists without opening the ZoomInfo platform.

Flowise
7 toolsManage low-code AI workflows via Flowise — run predictions, track chatflows and agentflows, handle tools, and audit execution history directly from any AI agent.

Lucidworks Fusion (AI Search & Discovery)
10 toolsManage AI-powered search via Lucidworks Fusion — execute semantic queries, index documents, and monitor ML training jobs.

Mambu
11 toolsManage clients, loans, deposits, and tasks on Mambu Cloud Banking Platform.
