Skip to main content
Book a demo

Connect DoorDash to Cline CLI

Give Cline CLI governed access to DoorDash’s 32 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add DoorDash to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 1

    Approve DoorDash in Runlayer

    Add DoorDash from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches DoorDash’s 32 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to DoorDash

    Each user signs in to DoorDash with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use DoorDash from Cline CLI

    DoorDash’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

32 DoorDash tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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.

See all 32 DoorDash tools

Control

What Runlayer can see and stop in Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every DoorDash call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI 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 Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination