Connect DoorDash to VS Code
Give VS Code governed access to DoorDash’s 32 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DoorDash to VS Code in four steps
Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.
- 1
Approve DoorDash in Runlayer
Add DoorDash from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect VS Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, DoorDash’s 32 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 3
Sign in to DoorDash
Each user signs in to DoorDash with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use DoorDash from VS Code
DoorDash’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
32 DoorDash tools in VS Code
Runlayer policy decides which of these VS Code users can call. 10 read data only.
Get meal manager calendars
List the corporate Meal Manager (DoorDash for Work) calendars the authenticated consumer has access to, and the dated group carts on each one.
Add to cart
Add items from a restaurant's menu to the consumer's cart, creating or updating the cart.
List delivery addresses
Get all saved delivery addresses for the authenticated consumer.
Set delivery address
Set the default delivery address for the authenticated consumer.
Find address
First step of adding a NEW delivery address: resolve a free-text street address into concrete candidates for the user to confirm.
Save address
Second step of adding a NEW delivery address: save the address the user confirmed (by place_id from a prior find_address result).
Get cart
Retrieve the consumer's cart.
Remove cart item
Remove a specific item from the consumer's cart.
Control
What Runlayer can see and stop in VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every DoorDash call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before VS Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before VS Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.
Frequently asked questions
Connect more
