DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
claude mcp add --transport stdio jordandalton-doordash-mcp-server node <thePathToYour>/build/index.js \ --env DOORDASH_API_KEY="<REPLACE>"
How to use
This MCP server integrates with the DoorDash API by providing a Node.js-based service you can include in your MCP client configuration. After building, you’ll get a ready-to-use index.js entry point that reads the DOORDASH_API_KEY from the environment to authenticate requests. The generated MCP JSON snippet (as shown in the build output) can be pasted into your MCP client (Claude Desktop, Windsurf, Cursor, etc.) to enable DoorDash-related data access through the MCP framework. The server is designed to be invoked with Node and will expose endpoints or actions defined by the build, driven by the provided API key.
To use the toolset, install dependencies, build the project, and then deploy the resulting Node entry point. Ensure the DOORDASH_API_KEY is set in your environment so that the server can authorize requests to the DoorDash API. Once configured, restart the MCP client or the server process to apply the new configuration and begin interacting with DoorDash data through the MCP ecosystem.
If you need to update credentials or scope, regenerate the build (npm run build) after updating your API key, and replace the DOORDASH_API_KEY value in the generated MCP JSON before loading it into your client.
How to install
Prerequisites:
- Node.js and npm installed on your machine
- Git (optional, for cloning the repository)
- Access credentials for the DoorDash API (DOORDASH_API_KEY)
Steps:
-
Clone or download the MCP server repository.
-
Navigate to the project folder in your terminal.
-
Install dependencies:
npm install
-
Build the TypeScript sources to generate the build directory and the MCP JSON snippet:
npm run build
-
Obtain your DOORDASH_API_KEY from DoorDash and set it in your environment or replace the placeholder in the generated MCP JSON before importing into your MCP client.
-
Copy the generated MCP JSON (containing the doordash server configuration) into your MCP client configuration as needed, or run the server locally using the produced build/index.js path if you’re running directly from Node.
Notes:
- If you modify environment variables or API scopes, re-run npm run build and update the MCP configuration accordingly.
Additional notes
Environment variables: DOORDASH_API_KEY is required for authenticating with the DoorDash API. Ensure it is kept secure and not committed to source control.
Common issues:
- Build failures due to TypeScript compilation: verify TypeScript and dependencies are correctly installed, and that the Node.js version is compatible.
- Invalid or missing API key: ensure the DOORDASH_API_KEY is correct and has the necessary permissions.
- Path issues: the MCP client expects the built index.js path; ensure the path placeholder in the generated JSON is correctly replaced with your actual build path.
Configuration tips:
- Keep your API key out of logs by relying on environment variables.
- If you deploy via container or a managed environment, pass DOORDASH_API_KEY through your deployment configuration.
- Validate the generated MCP JSON by loading it into your MCP client and testing a simple fetch to verify connectivity.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud
google-earth-engine
MCP server for Google Earth Engine. Query Google Earth Engine with natural language. Fetch datasets, run tasks and visualize in chat.