
Doordash
io.github.markswendsen-codePublished by GitHub account markswendsen-codev0.4.1Updated Oct 24, 2026
MCP server for DoorDash - let AI agents order food delivery autonomously with browser-based ordering
Overview
A local MCP server that lets an AI assistant search DoorDash restaurants, browse menus, build a cart, place food delivery orders and track them.
- What you can do
- Search restaurants by name, cuisine or food type and browse menus with item details and prices. Add items to a cart with quantities and special instructions. Place delivery orders with a confirmation step and track their status. Keep a persistent, per-user login session across restarts, with automatic multi-factor authentication handling.
- When to use it
- Useful when you want an assistant to handle everyday DoorDash ordering end to end — finding nearby restaurants, comparing menus and placing a delivery order — rather than just looking things up. Best for users who already have a DoorDash account and are comfortable letting an agent act on it.
- Requirements
- Runs locally as a Node.js process (Node.js 18 or later) via the npm package, typically launched with npx from the Claude Desktop config. Needs a DoorDash account, supplied through the DOORDASH_EMAIL and DOORDASH_PASSWORD environment variables, plus DOORDASH_ADDRESS for the delivery location. Desktop only; requires network access and a browser automation runtime.
Installation
In SourceWeft
- Open Doordash in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@striderlabs/mcp-doordash
Order food delivery via DoorDash using AI agents
[npm] [MCP Registry] [Claude Desktop] [License: MIT]
Part of Strider Labs — action execution for personal AI agents.
Get Started in 2 Minutes
For Claude Desktop Users
- Add this to
~/.openclaw/config.jsonor your Claude Desktop config:
- Restart Claude.
- Tell Claude: "Order Thai food from nearby for delivery today"
Your agent can now place orders. That's it.
Installation (NPM)
Or with npx directly:
Features
- 🔍 Search restaurants by name, cuisine, or food type
- 📜 Browse menus with full item details and prices
- 🛒 Add to cart with quantity and special instructions
- 💳 Place orders with confirmation step
- 📍 Track orders with real-time status updates
- 🔐 Persistent sessions - stay logged in across restarts
- 🔄 Automatic MFA - handles multi-factor authentication
- 📱 Per-user credentials - encrypted session storage
Tested & Compatible
Metrics
- Weekly downloads: 395 (Apr 10-17, 2026) — #1 Strider Labs connector (+24% growth)
- Status: ✅ Live in production
- Reliability: 85%+ task completion rate
- Discovery: npm, Claude Plugins, mcpservers.org, ClawHub, PulseMCP
Available Elsewhere
- npm: npmjs.com/@striderlabs/mcp-doordash
- Claude Plugins: Search "Strider Labs" in Claude
- mcpservers.org: Strider Labs DoorDash
- Full Strider Labs: github.com/striderlabsdev/striderlabs
How It Works
For Agents
Your agent can use these capabilities:
Session Management
- Each user has encrypted, persistent credentials
- Automatic OAuth token refresh
- MFA handling (SMS/email)
- Sessions survive agent restarts
Reliability
- 85%+ task completion rate
- Automated UI change detection (connectors update when DoorDash changes)
- Fallback paths for failures
- 24/7 monitoring + alerting
Configuration
Environment Variables
Self-Hosted
Architecture
How We Connect
This connector uses browser automation (Playwright) to interact with DoorDash, because DoorDash doesn't have a public API. Here's why that's safe and reliable:
- User-controlled: Your agent only accesses your own DoorDash account
- Session-based: We store your login session securely, not your password
- Change-aware: We detect DoorDash UI changes and alert immediately
- Fingerprinting: We use realistic browser profiles to avoid bot detection
- Rate-limited: We respect DoorDash's infrastructure with appropriate delays
Security
- Credentials stored encrypted in your local
.envor secure vault - Sessions isolated per user
- No data sent to third parties
- MIT Licensed — audit the code yourself
Support
Contributing
We welcome contributions! Areas of interest:
- Bug reports and fixes
- Feature requests (new restaurants, cuisines, etc.)
- Performance improvements
- Documentation enhancements
See CONTRIBUTING.md for guidelines.
License
MIT — Free to use, modify, and distribute. See LICENSE for details.
Built by Strider Labs — Making AI agents actually useful.
Source: README.md at commit 9a6fe59
Tools
0Version history
1- v0.4.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.