DoorDash MCP Server
by chaituredd
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to use when using HTTP transport. Default is '3000'. | 3000 |
| TRANSPORT | No | Transport protocol to use: 'stdio' or 'http'. Default is 'stdio'. | stdio |
| DOORDASH_KEY_ID | No | DoorDash Key ID from the Developer Portal. Required when DOORDASH_API_MODE is 'live'. | |
| DOORDASH_API_MODE | No | API mode: 'mock' or 'live'. Default is 'mock'. | mock |
| DOORDASH_DEVELOPER_ID | No | DoorDash Developer ID from the Developer Portal. Required when DOORDASH_API_MODE is 'live'. | |
| DOORDASH_SIGNING_SECRET | No | DoorDash Signing Secret from the Developer Portal. Required when DOORDASH_API_MODE is 'live'. |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues