@kody/doordashFork

@kody/doordash

Intent

Reusable DoorDash consumer helpers so Kody agents can search restaurants, browse menus, manage carts, and place orders for the caller's DoorDash account — the same consumer MCP gateway that powers dd-cli.

Auth is a saved access token from dd-cli export-token (waitlist account). Cart/order mutations default to dry-run and need confirm: true to run live.

This is not DoorDash Drive (Dasher logistics). That lives at @kody/doordash-driver.

This listing is meant to be forked. After you fork, call ./adapt, save your own token, and publish your copy.

Share this package as https://kody.codes/@kody/doordash

What it does

• Call DoorDash consumer MCP (openapi.doordash.com/mcp/consumerc)
• Search restaurants, menus, retail/grocery discovery
• Cart list/show/add/remove/clear
• Order history, preview, checkout URL, submit, reorder, status, receipt
• Addresses, payment methods, promos
• tools/list + generic call-tool escape hatch

Prerequisites / setup

1. Join the DoorDash CLI waitlist if needed: https://forms.gle/gvCQZvu9C1EKA6aM6
2. Install dd-cli from GitHub Releases, run dd-cli login, then dd-cli export-token.
3. Save the token (never paste it in chat):

https://kody.codes/account/secrets/new?name=doorDashCliAccessToken&description=DoorDash%20dd-cli%20access%20token%20from%20export-token%20(DD_CLI_ACCESS_TOKEN)&allowedHosts=openapi.doordash.com&scope=user

4. Approve host openapi.doordash.com on that secret.
5. Agents: see AGENTS.md. Start with ./smoke-test then ./search.

Adapt this fork

After community_fork, import ./adapt and follow its steps. Owner tokens stay in Kody secrets so the official @kody listing does not change.

License

MIT