DoorDash MCP Server
Related Servers
Alternatives to DoorDash MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to quote, schedule, dispatch, and track DoorDash Drive deliveries for restaurants and stores, including staggered batch scheduling for catering runs and launch nights, an operations board, and diagnostics check-ins. Actions that spend money or cancel work require explicit user confirmation, while quotes, tracking, and planning run freely.17MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search restaurants, place delivery orders, and track real-time delivery status using the DoorDash Drive API. It includes a built-in mock data mode that allows for testing and demonstrating delivery lifecycles without requiring live API credentials.MIT
- AlicenseBqualityDmaintenanceEnables AI agents to search restaurants, browse menus, manage carts, and place orders on DoorDash programmatically. It utilizes a headless browser to interact with DoorDash's GraphQL API and bypass anti-bot protections for the full delivery lifecycle.226 npm4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants in Cursor and other MCP hosts to connect to a company REST API, handling token-based authentication, read-only lookups, and guarded job/package creation with optional shipping labels.4 npmMIT
- AlicenseAqualityCmaintenanceEnables an AI assistant to browse restaurants and menus, manage a cart, reorder past orders, review checkout details, and place food delivery orders, returning a payment link to complete payment.13MIT
- AlicenseAqualityAmaintenanceEnables delivery tracking through the Parcel API, including listing and fetching deliveries, searching carriers, and adding new deliveries with optional write protection and multiple credential methods.55 npmMIT
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.