-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Luis Vervaet edited this page Aug 7, 2026
·
2 revisions
A REST implementation of the DoorDash Consumer MCP server.
The README covers installing and running it. Everything else lives here.
| Page | What is in it |
|---|---|
| Logging in | The paste-back OAuth flow, step by step, and why it works that way. |
| Device pairing | RFC 8628-style pairing for a TV, a headless box, or anything awkward to paste URLs into. |
| Sessions | Silent renewal, how long a session lives, what is stored and what protects it, and the lifetime settings. |
| Endpoints | Every route, the tool behind it, locations, optional parameters, errors, and response shapes. |
| Development | Running the tests and a map of the source. |
- Just want it running? README → Quick start, Docker or Unraid.
- Logging in for the first time? Logging in.
- Signing in a device with no browser? Device pairing.
- Wondering why you are being asked to log in again? Sessions.
-
Looking for a parameter? Endpoints, or the live Swagger UI
your instance serves at
/docs.
/docs is generated from the running instance's own route definitions, so it is
always accurate for the version you are on. These pages explain the why; the
/docs page is the reference.
ddREST is not affiliated with, endorsed by, or supported by DoorDash, and access to the MCP server is gated by DoorDash's own allowlist. See the README for the full statement — it applies to everything documented here.