LabscoMCP early access ↗
amannmMCP SERVER

DoorDash MCP Server

Quote, book and track a DoorDash Drive delivery from your own application's conversation.

by amannm ↗Food, Dining & DeliveryCommunity

LABSCO SUMMARY

Quote first, commit second — the two-step the Drive API expects.

Splitting create_delivery_quote from accept_delivery_quote is what makes this usable from a conversation: the price comes back before anything is dispatched, and the tip is decided at acceptance. Because it is a thin pass-through, the field names and semantics are DoorDash's own — helpful if you already know the API, and a reason to keep its documentation open if you do not.

What it is

A minimal bridge between the DoorDash Drive API and MCP clients. It passes requests through with little transformation, so what you get is the Drive API's own behaviour.

What you get

  • A delivery quoted from a pickup and dropoff address before anything is committed (create_delivery_quote)
  • A quote accepted, with a tip included if you want one (accept_delivery_quote)
  • A delivery created outright, with business names, contact numbers, pickup and dropoff instructions and order value (create_delivery)
  • The status of an existing delivery, looked up by the identifier you assigned it (get_delivery)
  • Addresses, times and other details changed after the fact (update_delivery)
  • A pending delivery cancelled (cancel_delivery)

Requirements

DoorDash Drive API access, which is a business partnership rather than a signup, and the credentials it issues — supplied as environment settings. Node.js. Every call is keyed on an external delivery identifier you choose.

Setup effort

Build from source — git clone https://github.com/amannm/doordash-mcp.git