Merge Unified's DoorDash integration Merge Agent Handler's DoorDash MCP server

Connect your AI Agents to DoorDash in minutes

Merge lets you securely connect your agents to DoorDash and thousands of tools instantly

Start building for free

Read docs

DoorDash

Learn more about Merge Agent Handler

Available tools

create_business

Create a DoorDash Drive business with an external ID, name, and optional description. Use list_businesses to verify creation.

list_businesses

List DoorDash Drive businesses with pagination. Use cursor from page_info for next page.

get_business

Get a DoorDash Drive business by its external business ID. Use list_businesses to find valid IDs.

update_business

Update a DoorDash Drive business name, description, or activation status. Use get_business to verify changes.

create_delivery

Create a DoorDash Drive delivery with pickup/dropoff details, phone numbers, and order info. Returns delivery with tracking URL.

get_delivery

Get a DoorDash Drive delivery by external delivery ID. Returns status, tracking URL, dasher info, and timestamps.

update_delivery

Update a delivery's instructions, dropoff phone, or tip. Use get_delivery to verify changes.

cancel_delivery

Cancel a DoorDash Drive delivery by external delivery ID. Cannot cancel delivered orders.

create_quote

Get a delivery quote with pickup/dropoff addresses, phone numbers, and order details. Returns estimated fee and times.

accept_quote

Accept a delivery quote by external delivery ID. Optionally update tip or dropoff phone. Creates the delivery.

create_store

Create a store under a DoorDash Drive business with name, phone, and address. Use list_stores to verify.

list_stores

List stores under a DoorDash Drive business with pagination. Use cursor from page_info for next page.

get_store

Get a store by business and store ID. Use list_stores to find valid store IDs.

update_store

Update a DoorDash Drive store name, phone number, or address. Use get_store to verify changes.

validate_credential

Validate DoorDash credentials by listing businesses. Returns {success, message}.

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's DoorDash MCP server

What is a DoorDash MCP?

A DoorDash MCP is an MCP server that connects your agents to DoorDash Drive via tools. Your agents can invoke these tools to create and cancel deliveries, generate and accept delivery quotes, manage store records, and more.

DoorDash doesn't offer an official MCP server, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the DoorDash MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

Automated delivery creation: When a new order is confirmed in your e-commerce platform, an agent creates a DoorDash Drive delivery automatically, passing pickup and dropoff details without any manual dispatch step

Quote-based fulfillment routing: An agent generates a delivery quote for an order, evaluates cost and estimated pickup time, and conditionally accepts or routes to an alternative carrier based on predefined thresholds

Delivery status syncing: An agent polls active deliveries, detects status changes like dasher assignment or arrival, and pushes updates to a customer-facing order tracker or internal ops dashboard

Cancellation and redelivery handling: When a fulfillment issue is detected in a warehouse system, an agent cancels the in-flight DoorDash delivery and immediately creates a replacement once the item is available

What are popular tools for DoorDash's MCP server?

Here are some of the most commonly used tools:

create_delivery: submits a new delivery request to DoorDash Drive with pickup and dropoff details. Use this when an agent needs to dispatch a delivery automatically after an order or fulfillment event

get_delivery: retrieves the current status of a delivery, including dasher assignment and tracking URL. Helpful when an agent needs to check progress before taking a downstream action like notifying a customer

cancel_delivery: cancels an active delivery that has not yet been picked up. Call this when an agent detects an inventory issue or order cancellation that requires stopping dispatch mid-flight

create_quote: generates a delivery quote for a given pickup and dropoff location, returning estimated cost and timing. Good for workflows that evaluate fulfillment options before committing to a delivery

update_delivery: modifies an existing delivery record, such as updating dropoff instructions, tip amount, or contact details. Useful for agents that apply last-minute changes from a customer update before pickup

list_stores: returns all stores associated with a DoorDash Drive business. Call this when an agent needs to identify the right pickup location before creating or routing a delivery

What makes Merge Agent Handler's DoorDash MCP server better than alternative DoorDash MCP servers?

Building on a community MCP server or self-hosting your own is one option, but here is why teams choose Merge Agent Handler's DoorDash MCP server instead:

Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For DoorDash, this means you can prevent customer contact details, delivery addresses, and payment-related metadata from being exposed even when the agent has broad read access

Managed authentication and credentials: Merge stores and refreshes DoorDash credentials on your behalf. You never expose raw API keys or signing secrets to an agent or manage credential rotation manually

Real-time observability and audit trail: Every tool call made against DoorDash is logged with timestamp, tool name, input parameters, and response metadata. You can audit exactly what an agent created, updated, or cancelled without instrumenting anything yourself

Tool Packs and controlled access: Tool Packs let you bundle specific DoorDash tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's DoorDash MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the DoorDash connector. Choose which tools to include: enable read tools for status monitoring use cases, or add write tools if your agent needs to create, update, or cancel deliveries.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate DoorDash by completing the credential flow. Merge stores and manages the credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your DoorDash tools are now accessible through that endpoint.

Can employees use Merge Agent Handler to connect their AI tools to DoorDash?

Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to DoorDash without bypassing IT governance.

Instead of setting up direct connections with personal credentials that IT can't monitor or revoke, each employee authenticates through Agent Handler and gets individual credentials tied to their identity.

IT also provisions access by role or group via SCIM. An ops manager, for example, gets DoorDash access to oversee delivery operations, Slack to coordinate with dispatch teams, and Google Sheets to report on fulfillment metrics; while a logistics coordinator gets DoorDash access to monitor active deliveries, Zendesk to handle customer escalations, and PagerDuty to respond to fulfillment failures.

Every tool call an employee's AI makes to DoorDash is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.