Peckish — DoorDash ordering MCP Server

What the code does

We read the source, 2 h ago · rules 3dff92dd89df

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    execFile(bin, ["--json-output", "address", "list"], { timeout: 30_000 }, (err, stdout, stderr) => {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add peckish -- npx -y peckish-mcp

{
  "mcpServers": {
    "peckish": {
      "args": [
        "-y",
        "peckish-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.peckish]
command = "npx"
args = ["-y", "peckish-mcp"]

{
  "mcpServers": {
    "peckish": {
      "args": [
        "-y",
        "peckish-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "peckish": {
      "args": [
        "-y",
        "peckish-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: DD_CLI_PATH (Absolute path to the dd-cli binary. Only needed if it is not at ~/.local/bin/dd-cli — GUI clients do not inherit your shell PATH.). The author declared them in the registry entry; get the values from the project itself.