doordash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doordash_loginA | Log into DoorDash. Reads credentials from ~/.doordash-mcp/config.json. Returns success or requests MFA code. |
| doordash_verifyC | Complete DoorDash login with a verification code. |
| doordash_searchB | Search for restaurants on DoorDash by name, cuisine, or food type |
| doordash_menuA | Get a restaurant's menu by store ID. Use doordash_search first to find the store ID. |
| doordash_convenience_searchC | Search for items within a convenience store (grocery, alcohol, pharmacy, etc.). |
| doordash_item_optionsA | Get customization options for a menu item (sides, extras, modifications). |
| doordash_add_to_cartB | Add an item to your DoorDash cart. For restaurants, pass item_name. For convenience stores, pass item_id directly. |
| doordash_cartA | View your current DoorDash cart contents and totals |
| doordash_modify_cartB | Modify cart: change item quantity or remove items. |
| doordash_delete_cartC | Delete a cart. |
| doordash_checkoutA | Preview checkout details (fees, total). Does NOT place the order. |
| doordash_place_orderA | Place a DoorDash order. THIS WILL CHARGE YOUR CARD. |
| doordash_order_statusC | Check the status of a DoorDash order |
| doordash_ordersB | Get recent DoorDash order history |
| doordash_payment_methodsB | List saved payment methods |
| doordash_add_cardC | Add a payment card to DoorDash. |
| doordash_addressesB | List saved delivery addresses |
| doordash_add_addressC | Add a delivery address. |
| doordash_set_addressC | Set the active delivery address. |
| doordash_create_group_orderC | Create a group order at a restaurant. Returns a share link. |
| doordash_group_order_statusB | View a group order's items broken down by person. |
| doordash_join_group_orderA | Join a group order as a guest on behalf of another user. Creates a guest session that can be used with doordash_add_to_cart. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Most tools have distinct purposes, but cart operations present minor risk: doordash_modify_cart can remove individual items while doordash_delete_cart clears the entire cart, which could confuse agents. Group order tools and search variants are well-differentiated by their descriptions.
Significant inconsistency in naming patterns: roughly half use verb_noun (add_to_cart, place_order, set_address) while others use noun-only or noun_noun (cart, addresses, menu, payment_methods, group_order_status). The prefix is consistent, but internal structure varies widely between verb-first and noun-first conventions.
With 22 tools, this falls into the 'heavy' category (16-25 range). While it comprehensively covers the delivery lifecycle including group orders and convenience stores, the surface area is large enough that agents may struggle to select the optimal tool chain without careful reading.
Covers the full ordering lifecycle well: authentication with MFA, address/payment management, browsing (restaurants and convenience), cart operations, group orders, and order placement/status. Minor gaps exist (no cancel_order, delete_address, or delete_payment_method), but core workflows are fully supported.