DoorDash MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOORDASH_EMAIL | Yes | Your DoorDash account email address |
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 |
|---|---|
| login_checkB | Check if the DoorDash session is active |
| search_restaurantsC | Search for restaurants and food on DoorDash |
| get_store_menuC | Get a store's full menu with items and prices |
| add_to_cartC | Add an item to your DoorDash cart |
| remove_from_cartC | Remove an item from your DoorDash cart |
| list_cartsB | List all active DoorDash carts |
| order_historyB | Get recent DoorDash order history |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: cart management (add/remove/list), menu/restaurant lookup (get_store_menu/search_restaurants), session checking (login_check), and order history. The descriptions make it easy for an agent to select the right tool for specific tasks like browsing versus ordering.
The tools mostly follow a consistent verb_noun pattern (e.g., add_to_cart, get_store_menu, list_carts), with all using snake_case. The minor deviation is 'login_check' which uses a noun_verb structure instead of verb_noun, but this is a small inconsistency that doesn't significantly impact readability or predictability.
With 7 tools, this server is well-scoped for DoorDash operations, covering key actions like browsing, cart management, and order tracking. Each tool earns its place without redundancy, making it manageable for agents while providing comprehensive functionality for the domain.
The tool set covers core DoorDash workflows: browsing (search_restaurants, get_store_menu), cart management (add/remove/list), session handling (login_check), and order review (order_history). A minor gap is the lack of a tool to place an order or checkout from the cart, which could limit end-to-end automation, but agents can still perform most tasks effectively.