Dada Now Delivery MCP for AI. Manage local orders and store logistics instantly.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Dada Now Delivery integrates Dada Now's on-demand local logistics network directly into your AI client. Your agent can schedule full deliveries, calculate real-time routing fees, manage pickup hubs, and track order status—all from natural conversation.
It gives non-technical staff the ability to coordinate complex, multi-step delivery workflows.
What your AI can do
Add complaint
Sends a formal complaint regarding a specific delivery driver's performance.
Add order
Creates and dispatches a brand new Dada local delivery order.
Add shop
Registers a completely new physical location or shop to serve as a pickup hub.
Schedule new orders for local pickup or drop-off, track existing shipments live, and cancel dispatches when needed.
Estimate the full delivery fee before committing to an order by querying the route data.
Register new pickup locations or modify details for existing partner shops in the network.
Automatically add monetary tips to orders or submit formal complaints about driver performance.
Ask an AI about this
Waiting for input…
Dada Now Delivery: 10 Tools for Logistics Ops
These tools allow your AI client to handle the full lifecycle of local deliveries, from initial fee estimation to final complaint submission.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Dada Now Delivery on VinkiusAdd Complaint
Sends a formal complaint regarding a specific delivery driver's performance.
Add Order
Creates and dispatches a brand new Dada local delivery order.
Add Shop
Registers a completely new physical location or shop to serve as a pickup hub.
Add Tip
Adds a specific monetary tip payment to an active delivery order.
Cancel Order
Immediately cancels a scheduled or dispatched delivery run.
Get City Code
Retrieves the necessary Dada City Codes required to process any order request.
Query Order Fee
Estimates and returns the total delivery cost before an actual order is placed.
Query Order Status
Gets the current, live tracking status of any active shipment.
Readd Order
Reactivates a delivery order that has expired or failed to complete its route.
Update Shop
Modifies the details for an existing, registered shop or pickup station.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Dada Now Delivery, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Dada Now. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking local deliveries used to mean jumping between multiple dashboards.
Right now, if an order is delayed, you're forced to open the primary tracking portal. You check the status; it says 'delayed.' Then you have to switch tabs to the complaints module to file a report, and finally, if you need to change where the goods go, you manually navigate to the shop management section. It’s three separate systems just for one problem.
With this MCP integrated into your AI client, that whole sequence vanishes. You simply tell your agent about the delay. It pulls up `query_order_status` instantly, confirms the issue, and then runs `add_complaint` right there in the same conversation flow. It's one interaction, end-to-end.
Handling order fees is simple with Dada Now Delivery MCP.
Before placing an order manually, you have to guess at the cost or check a dedicated fee calculator page. If your agent doesn't confirm the price first, you risk sending a customer a final invoice that includes unexpected tolls and fees.
Now, your client runs `query_order_fee` first. It spits out the exact estimated toll immediately. You know the total cost right then, making the process transparent and trustworthy every single time.
What your AI can actually do with this
Your AI model suddenly acts like a field operations manager for local couriers. Instead of logging into a separate portal or calling an agent, your client handles logistics directly. You can tell it where goods need to go and instantly get an estimated cost using the fee calculator before actually creating the order.
Need to update a pickup point? Just ask it to register a new shop hub. It manages everything from scheduling deliveries to adding tips for riders, all while maintaining contact with the live network data. Because this MCP sits in the Vinkius catalog, your agent stays connected no matter which AI client you use—Claude, Cursor, or Windsurf.
This gives operations teams immediate control over complex delivery processes without needing to write a single line of integration code.
019d842c-3f12-737e-8b46-2de85f76f391 Here's how it actually works
The bottom line is, you pass credentials once, and your entire AI workflow can access complex, secure logistics functions immediately.
Sign up for the Dada Now Developer Program and gather your App Key, Secret, and Source ID.
Add those credentials safely into Vinkius. The platform handles the complex signing rules so your AI client never sees cryptography details.
Your AI agent uses the tools to execute logistics actions—like checking fees or adding a new order—and gets real-time responses back.
Who is this actually for?
This MCP is for the operations manager who spends hours clicking between scheduling dashboards to manually process orders. It’s for e-commerce platform owners whose customer service reps need immediate dispatch capability.
Needs to instantly confirm if a shipment is possible, estimate the cost of goods movement, and update store hours based on live data.
Must be able to take a customer's request, check the fees using query_order_fee, create the shipment with add_order, and handle complaints or tips without transferring the call.
Manages multiple pickup points, registering new hubs via add_shop or updating details for existing stations using update_shop.
What Changes When You Connect
You can dispatch couriers directly from a customer chat. No need for the customer to submit a web form; your agent handles add_order immediately.
Before committing an order, use query_order_fee to calculate exact costs and give the user immediate price transparency. This prevents bad orders right out of the gate.
The system supports dynamic operational adjustments. If there's a delay, your AI can automatically add a tip using add_tip or file a formal complaint via add_complaint.
Need to expand service areas? You can tell your agent to register new pickup points using add_shop, making the process conversational instead of manual form filling.
It gives non-technical staff control over core logistics. They can manage everything from tracking status with query_order_status to re-activating a failed shipment with readd_order.
See it in action
New Client Onboarding
A sales rep speaks to a prospective client and needs an instant quote. The agent calls the tool first to run query_order_fee, giving the prospect a precise price estimate immediately, letting them know exactly what's involved before sending any formal paperwork.
Dispute Resolution
A customer complains about late delivery. The agent doesn't just apologize; it uses query_order_status to check the real-time location and then uses add_complaint to formally report the delay, making the complaint actionable.
Network Expansion
The operations team needs a new pickup point in the district center. Instead of filling out a multi-page developer form, they simply tell their agent to use add_shop with the new address and name, which registers it instantly.
Handling Failed Deliveries
An order fails mid-route. Instead of waiting for a human operator, the agent spots the failure status and runs readd_order, bringing the shipment back into active dispatch without manual intervention.
The honest tradeoffs
Trying to manually update location data
A user tries to fix an old store address by copying and pasting changes into a general chat field, hoping the AI will guess what needs updating.
Don't try to patch it. Use the dedicated update_shop tool. This ensures you are modifying only specific station details, keeping your data clean.
Sending orders without cost validation
Dispatching an order immediately after a customer says 'yes,' risking over-delivery fees because the price wasn't confirmed first.
Always run query_order_fee first. Getting that quote verifies the route and the cost before you call add_order. It saves everyone time.
Confusing status checks with re-dispatch
Finding an order is canceled and trying to manually restart it by calling add_order again, which creates a duplicate record.
If the order failed or expired, check the tools. Use readd_order instead of creating a new one; this handles the history correctly.
When It Fits, When It Doesn't
Use this MCP if your core business loop involves physical goods moving from Point A to Point B and requires managing those steps conversationally. If you need to handle store location changes, calculate costs upfront, or process customer feedback (complaints/tips), this is the right fit. Don't use it if your entire workflow only involves simple data storage—you don't need add_shop if you never change hubs. And skip it entirely if you only need to read static information; for pure reading tasks, a simple database query tool would be better than needing full dispatch control.
Questions you might have
How do I use the add_order tool with Dada Now Delivery? +
You tell your agent to create an order. The agent will first need necessary location codes, so it may call get_city_code before running add_order to ensure all parameters are correct.
Can I update a shop using the update_shop tool? +
Yes. The update_shop tool lets you modify existing station details, so you don't have to re-register the entire location if only one detail changed.
What is the difference between query_order_fee and add_order? +
query_order_fee just gives an estimate—it reads data. add_order actually sends the dispatch request to the network, creating a live order.
How do I handle tips or complaints after delivery? +
For post-delivery actions, use add_tip if you want to add money to an existing order, or use add_complaint to file a formal report about the driver.
How do I use the `add_shop` tool if my pickup location needs to be registered first? +
You must run add_shop initially, providing all required hub details. Once that shop is successfully registered, your AI agent can reference its new ID for subsequent deliveries or updates.
My delivery failed or expired; how does the `readd_order` tool help me resume it? +
The readd_order function lets you resubmit an order that timed out, was canceled by the driver, or otherwise failed. You just need the original dispatch details to get the process moving again.
Before I use `add_order`, should I check city codes with the `get_city_code` tool? +
Yes. Running get_city_code first ensures your order payload uses valid geographical identifiers. This prevents common submission errors related to location mapping and routing.
How do I get real-time location updates using the `query_order_status` tool? +
You pass the specific order ID to this function, and it returns the current live status of the dispatch. Your AI agent can then surface this tracking information directly to the user.
Is the MD5 signature abstracted? +
Yes! The parameters like timestamp, app_key, v, and format are automatically concatenated. The backend performs the MD5 check and injects the signature transparently to the LLM context, yielding flawless delivery logs.
We've already built the connector for Dada Now Delivery. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.