DoorDash MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOORDASH_KEY_ID | Yes | Your DoorDash key ID | |
| DOORDASH_DEVELOPER_ID | Yes | Your DoorDash developer ID | |
| DOORDASH_SIGNING_SECRET | Yes | Your DoorDash signing secret |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_delivery_quoteC | Get a quote for a delivery request |
| create_deliveryC | Create a new delivery request |
| get_deliveryC | Get the status of an existing delivery |
| cancel_deliveryC | Cancel an existing delivery |
| accept_delivery_quoteC | Accept a delivery quote and optionally add a tip |
| update_deliveryC | Update delivery details such as addresses, times, or other parameters |
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 6 tools
Each tool has a clearly distinct purpose targeting specific actions in the delivery lifecycle: create_quote, accept_quote, create_delivery, get_delivery, update_delivery, and cancel_delivery. There is no overlap or ambiguity between these operations.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., create_delivery_quote, accept_delivery_quote, cancel_delivery). The naming is predictable and uniform throughout the set.
With 6 tools, this server is well-scoped for managing deliveries, covering the essential lifecycle from quoting to completion. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides complete CRUD/lifecycle coverage for the delivery domain: create (quote and delivery), read (get), update, and delete (cancel). There are no obvious gaps, and agents can handle typical workflows without dead ends.