Site icon Efficient Coder

Master DiDi MCP Integration: Your Complete Guide to Ride-Hailing API Success

高效码农

DiDi MCP: A Complete Guide to Integrating Ride-Hailing Capabilities into Your Applications

The way we move around cities has changed dramatically in the past decade. Ride-hailing platforms transformed from standalone apps into essential digital infrastructure. DiDi, one of the world’s leading mobility companies, has now taken a new step by opening its ride-hailing capabilities through MCP (Mobility Capability Platform).

MCP allows developers and businesses to embed ride-hailing features—such as viewing available car types, estimating fares, placing orders, and tracking drivers—directly into their own applications or platforms. This blog post is a comprehensive guide to understanding, integrating, and making the most of DiDi MCP.

1. What is DiDi MCP?

DiDi MCP is an open platform service that packages DiDi’s core ride-hailing functions into developer-friendly interfaces. Instead of building transportation logic from scratch, developers can plug into MCP and instantly offer their users seamless ride-booking experiences.

This makes MCP more than just an API—it is a bridge between DiDi’s ecosystem and third-party applications, whether for personal projects, consumer-facing apps, or enterprise systems.

At its core, MCP enables four essential functions:

  • Discovering car options available in a region
  • Estimating fares before booking
  • Creating ride orders directly within an app
  • Managing the full lifecycle of a ride, including tracking and cancellations

2. Versions of DiDi MCP

DiDi MCP offers three different versions to accommodate a wide range of users. Each version provides specific levels of access and control.

2.1 Beta Version

  • Target Audience: Developers who want a lightweight integration or a quick start.
  • Capabilities:
    • Price estimation
    • Redirect users to DiDi App or Mini Program for booking
  • Use Case: Apps that want to show fare estimates and provide a direct “book now” button without handling full ride management.

2.2 Pro Version (For Individual Developers)

  • Target Audience: Independent developers or small teams.
  • Capabilities:
    • Create ride orders
    • Cancel orders
    • Contact drivers
  • Use Case: Voice assistants, smart devices, or custom ride-hailing experiences that require end-to-end booking directly inside the application.

2.3 Pro+ Version (For Enterprises)

  • Target Audience: Enterprises with large-scale or custom needs.
  • Capabilities:
    • Full customization of the ride-hailing process
    • Integration with corporate travel management systems
    • Automated expense management
  • Use Case: A corporate travel platform that automatically books rides for employees and integrates ride data into expense reports.

3. Getting Started with DiDi MCP

Integrating MCP into your system follows four straightforward steps.

Step 1: Register an Account

Create a DiDi account using a valid mobile phone number. Registration is done through the DiDi App or Mini Program.

Step 2: Activate MCP Key

Once registered as a developer, log into the console and activate your MCP Key. This key is your unique credential for authentication.

Step 3: Build the Request URL

The base endpoint for MCP is:

https://mcp.didichuxing.com/mcp-servers

Authentication requires appending your key as a URL parameter:

https://mcp.didichuxing.com/mcp-servers?key=YOUR_API_KEY

Step 4: Make API Calls

MCP uses Streamable HTTP with JSON-RPC 2.0 for communication.

Example request to list available tools:

curl -X "POST" "https://mcp.didichuxing.com/mcp-servers?key=YOUR_API_KEY" \
-H 'Content-Type: application/json; charset=utf-8' \
-d '{
  "jsonrpc": "2.0",
  "method": "tools/list",
  "id": 1,
  "params": {
    "_meta": {
      "progressToken": 1
    }
  }
}'

4. MCP Capabilities and API Methods

MCP provides structured endpoints to manage the entire ride-hailing workflow. Below is a breakdown of its primary functions.

4.1 View Available Cars and Estimate Prices (taxi_estimate)

  • Purpose: Retrieve available ride categories and their estimated fares.
  • Use Case: Display fare options to users before they confirm a booking.

Parameters:

Name Type Required Description
from_lng string Yes Pickup longitude
from_lat string Yes Pickup latitude
from_name string Yes Pickup name
to_lng string Yes Drop-off longitude
to_lat string Yes Drop-off latitude
to_name string Yes Drop-off name

4.2 Generate Ride Link (taxi_new_order) — Beta Only

  • Purpose: Generate a ride link that opens DiDi App or Mini Program to complete booking.
  • Use Case: Minimal integrations where you don’t need in-app booking.

Required Parameter Example:

  • product_category: Array of car types retrieved from taxi_estimate.

4.3 Create Ride Order (taxi_create_order) — Pro Only

  • Purpose: Place a ride order and assign a driver.
  • Use Case: In-app ride booking without redirection.

Parameters:

Name Type Required Description
product_category string Yes Car type identifier
estimate_trace_id string Yes ID from fare estimate step
caller_car_phone string Yes Passenger phone number

4.4 Query Ride Order (taxi_query_order) — Pro Only

  • Purpose: Check ride order status and driver details.

  • Information Returned:

    • Driver contact info
    • Estimated arrival time
    • Distance and vehicle details

Required Parameter: order_id

4.5 Cancel Ride Order (taxi_cancel_order) — Pro Only

  • Purpose: Cancel an active order.
  • Required Parameter: order_id

4.6 Get Driver Location (taxi_get_driver_location) — Pro Only

  • Purpose: Fetch real-time GPS coordinates of the assigned driver.
  • Use Case: Show driver’s live location on an in-app map.

Required Parameter: order_id

5. Version Release Notes

  • v1.0.0 (2025-08-01): Initial release with ride estimation and ordering.
  • v1.0.2 (2025-08-18): Pro version added with expanded MCP services.

6. Practical Applications

MCP’s flexibility allows it to fit into a variety of real-world scenarios.

Individual Developer Example

A solo developer creates a voice-controlled assistant that books rides through simple commands like “Book me a ride to the airport.” With MCP Pro, the assistant can handle everything: estimate fares, confirm the booking, and notify when the driver arrives.

Enterprise Example

A company integrates MCP Pro+ into its travel management system. Employees request rides through the internal platform, and all expenses are automatically logged for reimbursement. The entire process—from booking to accounting—is automated.

7. Benefits of MCP Integration

  • Unified Experience: Users stay inside your app while accessing ride-hailing features.
  • Efficiency: Automated ride booking saves time and reduces friction.
  • Customization: Choose the version (Beta, Pro, or Pro+) that fits your technical and business needs.
  • Scalability: From personal tools to enterprise platforms, MCP adapts to different scales of use.
City transport

8. Conclusion

DiDi MCP transforms ride-hailing into an accessible capability for developers and businesses.

  • The Beta version offers lightweight integration through links.
  • The Pro version empowers individuals to build custom ride experiences.
  • The Pro+ version enables enterprises to fully automate and integrate transportation into their operations.

By following the setup process and mastering the available APIs, you can deliver seamless mobility solutions inside your applications. MCP is not just a set of tools; it is a new way to expand the reach of ride-hailing services into diverse digital ecosystems.

Exit mobile version