Skip to main content

Get started with DoorDash MCP

Private beta

DoorDash MCP is in private beta. Access is currently limited to approved testers.

Want in? Join the waitlist and we'll reach out regarding next steps.

This guide connects a generic MCP client to DoorDash and calls a first read-only tool.

1. Join the waitlist​

DoorDash MCP is in private beta. Join the waitlist to request access. Once approved, DoorDash will provision an OAuth client for your agent. The client will be configured for typical integration points, if you have any custom redirect_uri or agent harnesses please mention in the application.

2. Install and set up your MCP client​

DoorDash will reach out after approval with installation and setup instructions for your MCP client.

3. Authorize with DoorDash OAuth​

The first time your agent connects, the consumer using your product will need to log into DoorDash and authorize the MCP connection. DoorDash uses standard OAuth v2.1 with PKCE. After the token exchange, your agent can attach the access token within the authorization header for MCP access.

4. Call a tool​

Once authorized, list the tools available to your client, then call one:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_restaurants",
    "arguments": {
      "query": "ramen"
    }
  }
}

A successful response returns structured JSON your agent can reason over directly. See Available tools for the full corporate-ordering tool set, including the cart and order-placement tools.

Safe first steps​

To try a full ordering flow without charging anyone:

  1. find_restaurants → get_restaurant_menu → add_to_cart
  2. preview_order to see pricing and totals
  3. clear_cart to clean up instead of calling submit_order

Only call submit_order after the consumer has explicitly confirmed they want to place the order — it charges their payment method for real.